Request for Proposal for e Ticketing Project - Archaeological Survey ...

Request for Proposal for e 

Ticketing Project 

Archaeological Survey of India, Volume - 1 

Functional, Technical & Operational Requirements 

April 2013 

Submitted by 

National Institute for Smart Government 

April 2013

RFP for e-Ticketing Solution Volume-I 

Table of Contents 

1. Introduction & background ............................................................................................................. 9 

2. e-Ticketing Project ........................................................................................................................ 12 

2.1 Project Vision ........................................................................................................................ 12 

2.2 Project Overview ................................................................................................................... 12 

2.3 Project Objectives ................................................................................................................. 12 

3. Overview of Current State of Ticketing at the Monuments ......................................................... 13 

3.1 Key problems being faced by different stakeholders ................................................................. 13 

4. Project Requirements ................................................................................................................... 15 

4.1 Statement of Work................................................................................................................ 15 

4.2 Detailed Description of Requirements and Features ............................................................ 16 

5. Functional Requirements - E-ticketing System ............................................................................. 23 

5.1 Web based online ticket ........................................................................................................... 23 

5.1.1 Foreign Visitors ..................................................................................................................... 23 

5.1.2 Indian Visitors ....................................................................................................................... 24 

5.2 Tickets Sale at the counter / Point Of Sale (for Walk In Visitors) ............................................. 25 

5.2.1 Foreign Visitors ..................................................................................................................... 25 

5.2.2 Indian Visitors ....................................................................................................................... 25 

5.2.3 Validation / Authentication .................................................................................................. 25 

5.3 General ...................................................................................................................................... 26 

5.4 Non-functional requirements: .................................................................................................. 27 

6. Technical Architecture & Requirements ....................................................................................... 28 

Indicative E-Ticketing Solution Architecture ......................................................................................... 29 

7. Infrastructure Requirements ........................................................................................................ 40 

8. Operational Requirements............................................................................................................ 45 

9. Requirements of Project Implementation .................................................................................... 54 

10. Governance ............................................................................................................................... 62 

12. Documentation Requirements.................................................................................................. 67 

ANNEXURES .......................................................................................................................................... 69 

List of Monuments ................................................................................................................................ 69 

Bill of Quantity ...................................................................................................................................... 79 

Visitor Footfall Details ........................................................................................................................... 80 

Technical Specifications ........................................................................................................................ 94 

Enterprise Management System ........................................................................................................ 101 

Proposed Process Diagrams (indicative) ............................................................................................. 105 

Archeological Survey of India, Ministry of Culture Page 1 of 107


List of Tables 

TABLE 1: IMPORTANT DATES 8 

TABLE 2 : E-TICKETING SYSTEM STANDARDS 38 

TABLE 3 BANDWIDTH REQUIREMENT 44 

TABLE 4: RESPONSIBILITY MATRIX 54 

TABLE 5 : TIMELINES AND DELIVERABLES OF THE PROJECT 56 

TABLE 6: IMPLEMENTATION SCHEDULE 57 

TABLE 7: PROJECT DELIVERABLES 61 

List of Figures 

FIGURE 1: SOLUTION ARCHITECTURE 29 

FIGURE 2: NETWORK DIAGRAM 43 



List of Abbreviations 

AMC Annual Maintenance Contract 

ASI Archaeological Survey of India 

FRS Functional Requirement Specifications 

HLD High Level Design 

IA Implementation Agency 

IEEE Institute of Electrical and Electronics Engineers 

ISO International Standards Organization 

LLD Low Level Design 

NISG National Institute for Smart Government 

NOC No Objection Certificate 

PKI Public Key Infrastructure 

PMU Project Management Unit 

RFP Request for Proposal 

SLA Service Level Agreement 

SPOC Single Point of Contact 

SRS Software Requirement Specifications 

ETS E Ticketing Solution 

POS Point of Sale 



About this Request for Proposal 

This document constitutes the Request for Proposal (RFP) for selection of Implementation 

Agency (IA) by Archaeological Survey of India (ASI). This RFP has been prepared to invite 

bidders to submit their proposals to implement and maintain e Ticketing system for ASIs 

protected Monuments. 

Information used for the preparation of this RFP has been made available from relevant and 

published sources of information. Nonetheless, bidders are required to make informed 

evaluation and decision based on their judgment. 

This RFP document contains the entire information that constitutes the requirement as 

proposed by ASI in order for qualified bidders to submit their proposals. Any queries or 

clarifications must be submitted in the prescribed format and will be addressed to all 

bidders simultaneously. 

This RFP comprises the following documents: 

a) Volume-I : Functional, Technical and Operational Requirements 

b) Volume-II : Commercial and Bidding Terms 

c) Volume-III : Contractual and Legal Conditions 



Disclaimer 

This Request for Proposal (RFP) for Selection of Implementation Agency is issued by 

Archeological Survey of India under the Ministry of Culture, Government of India. 

Whilst the information in this RFP has been prepared in good faith, it is not and does not 

purport to be comprehensive or to have been independently verified. Neither ASI, nor any 

of its officers or employees, nor any of their advisers nor consultants accept any liability or 

responsibility for the accuracy, reasonableness or completeness of the information 

contained in the RFP, or for any errors, omissions or misstatements, negligent or otherwise, 

relating to the proposed ASI e- Ticketing Project, or makes any representation or warranty, 

express or implied, with respect to the information contained in this RFP or on which this 

RFP is based or with respect to any written or oral information made or to be made 

available to any of the recipients or their professional advisers and, so far as permitted by 

law and except in the case of fraudulent misrepresentation by the party concerned, and 

liability therefore is hereby expressly disclaimed. 

The information contained in this RFP is selective and is subject to updating, expansion, 

revision and amendment at the sole discretion of ASI. It does not, and does not purport to, 

contain all the information that a recipient may require for the purposes for making a 

decision for participation in this process. Each Party must conduct its own analysis of the 

information contained in this RFP, to correct any inaccuracies therein and is advised to carry 

out its own investigation into the proposed e –Ticketing Project, the regulatory regime 

which applies thereto and by and all matters pertinent to this Project and to seek its own 

professional advice on the legal, financial and regulatory consequences of entering into any 

agreement or arrangement relating to this Project. ASI shall not be responsible for any 

direct or indirect loss or damage arising out of or for use of any content of the RFP in any 

manner whatsoever. 

This RFP includes certain statements, projections, targets and forecasts with respect to the 

Project. Such statements, projections, targets and forecasts reflect various assumptions 

made by the management, officers, employees, consultants, and experts of ASI, which (the 

assumptions and the base information on which they are made) may or may not prove to be 

correct. No representation or warranty is given as to the reasonableness of forecasts or the 

assumptions on which they may be based and nothing in this RFP is, or should be relied on 

as, a promise, representation or warranty. 

ASI shall be the sole and final authority with respect to qualifying a bidder through this RFP. 

The decision of ASI in selecting the Implementation Agency who qualifies through this RFP 

shall be final and ASI reserves the right to reject any or all the bids without assigning any 

reason thereof. ASI further reserves the right to negotiate with the selected agency to 



enhance the value through this project and to create a more amicable environment for the 

smooth execution of the project. 

ASI may terminate the RFP process at any time without assigning any reason and upon such 

termination ASI shall not be responsible for any direct or indirect loss or damage arising out 

of such a termination. 



Contact Persons 

National institute of Smart Government (NISG) has been appointed as the Advisor to assist 

ASI in the preparation of this RFP, and the review of proposals received, and the selection of 

the eligible IA. All communication with regard to this RFP must be directed solely to the 

person and the address mentioned below. Any communication with a person other than 

the one mentioned below, would not be entertained and could result in the Application 

being considered as non-responsive. 

Contact Person Mr. Rajeev Sharma 

Address for Communication and Submission of bid Senior Administrative Officer 

Archaeological Survey of India 

Janpath, New Delhi - 110011 

Phone: +91-11-23018583 

Fax: +91-11- 23018583 

websiteasi@gmail.com 

Bid document availability Bid document can be downloaded from 

ASI website : www.asi.nic.in 

: www.nisg.org 

: www.eprocure.gov.in/cppp 



Important Dates 

Following are the key dates for bidding and selection process. 

Activity Date 

Release of RFP (Request for Proposal) April 26, 2013 

Last date for submission of questions by bidders May 03, 2013 

Pre-Bid Conference May 07, 2013 

Response to bidder queries May 13, 2013 

Last date for submission of Bids May 23, 2013 

Pre- Qualification Bid opening May 24, 2013 

Date for opening of Technical Bids for qualified bidders To Be Announced 

Date for Technical Presentations or Proof of Concept To be Announced 

Date for opening of Commercial Bids for qualified bidders To be Announced 

Award of Contract To be Announced 

Table 1: Important Dates 

Address for communication, collection and submission of bid forms are as given below:- 

Contact Details 

Contact Person Mr. Rajeev Sharma 

Address for Communication and Submission of bid Senior Administrative Officer 



Phone: +91-11-23018583 

Fax: +91-11- 23018583 


Bid document availability Bid document can be downloaded from 

ASI website : www.asi.nic.in 

: www.nisg.org 

: www.eprocure.gov.in/cppp 



1. Introduction & background 

The Archaeological Survey of India (ASI), is a well-established organization for archaeological 

research under the Ministry of Culture, and plays a significant role in protecting the cultural 

heritage of the Country. Conservation of ancient monuments, archaeological sites and 

excavations remains of national importance and are the prime concerns of ASI. 

Estalished i 8, oe the eas, A“Is sope has epaded to a lage ue of fields 

such as preservation, conservation, architectural studies, epigraphy, horticultural and 

environmental up-gradation and underwater archaeology. ASI regulates all archaeological 

activities in the country as per the provisions of the Ancient Monuments and Archaeological 

Sites and Remains Act, 1958. ASI also regulates Antiquities and Art Treasure Act, 1972. At 

present, ASI protects 3,678 monuments including 21 World Heritage Cultural Properties 

besides, and also maintains 44 museums around the country. 

ASI now wishes to commission an integrated IT enabled e ticketing system across all 

protected Monuments under ASI in order to ensure transparent, easy, efficient operations 

of Ticketing and also enhance visitor experience. 

In this context, ASI has engaged National Institute for Smart Government (NISG) for 

consulting services, which include a detailed study of existing ASI operations and to propose 

feasible solutions that can be adopted by ASI in the near future. 

As part of the tender process, ASI is releasing this RFP to receive responses from eligible 

bidders, to evaluate the bids and select the most appropriate Implementing Agency (IA). 



About Archeological Survey of India 

ASI is divided into 24 Circles and 1 mini Circle (refer to Annexure for the Circle Details) for 

the maintenance of ancient monuments, archaeological sites which remains of national 

importance. ASI carries out elaborate surveys of antiquarian remains in the country and 

protects monuments and sites. ASI has a large work force comprising of trained 

archaeologists, conservators, epigraphist, architects and scientists for conducting 

archaeological research projects through its Circles, Museums, Excavation Branches, 

Prehistory Branch, Epigraphy Branches, Science Branch, Horticulture Branch, Building Survey 

Project, Temple Survey Projects and Underwater Archaeology Wing. 

The Circles carry out archaeological fieldwork, research activities and implement various 

activities which include: 

Extensive survey of antiquarian remains in villages of India. 

Exploration of archaeological sites and documentation of sculptures. 

Excavation of archaeological sites. 

Conservation and day-to-day maintenance of protected monuments. 

Providing basic facilities at the monuments for tourists. 

Issuing of NOC for any sort of construction, additions and alterations to existing structures 

or new constructions within regulated area of the protected monuments. 

Issuing permission for filming, photography and cultural programs at the protected 

monuments. 

Organizing public awareness programs on various occasions like Word Heritage Day, World 

Heritage Week, Museum Day and other important occasions. 

Registration of antiquities and issuing non-antiquity certificates. 

Interaction with various universities and research institutions. 

The Archaeological Survey of India (ASI), under the Ministry of Culture, is the premier 

organization for the archaeological researches and protection of the cultural heritage of the 

nation. Maintenance of ancient monuments, archaeological sites and remains of national 

importance is the prime concern of the ASI. Besides, it regulates all archaeological activities 

in the country as per the provisions of the Ancient Monuments and Archaeological Sites and 

Remains Act, 1958. It also regulates Antiquities and Art Treasure Act, 1972. 



1. About Monuments 

The Ancient Monuments and Archaeological Sites and Remains Act, 1958 defines an 

Aiet Mouet as follows:- 

Ancient Monument means any structure, erection or monument, or any tumulus or place of 

interment, or any cave, rock-sculpture, inscription or monolith which is of historical, 

archaeological or artistic interest and which has been in existence for not less than 100 

years and includes 

- Remains of an ancient monument, 

- Site of an ancient monument, 

- Such portion of land adjoining the site of an ancient monument as may be required for 

fencing or covering in or otherwise preserving such monument, 

- The means of access to, and convenient inspection of, an ancient monument; 

There are at present more than 3650 ancient monuments and archaeological sites and 

remains of national importance. These monuments belong to different periods, ranging 

from the prehistoric period to the colonial period and are located in different geographical 

settings. They include temples, mosques, tombs, churches, cemeteries, forts, palaces, stepwells, 

rock-cut caves, and secular architecture as well as ancient mounds and sites which 

represent the remains of ancient habitation. 

These monuments and sites are maintained and preserved through various Circles of the ASI 

spread all over the country. The Circles look after the research on these monuments and 

conservation activities, while the Science Branch with its headquarters at Dehradun carries 

out chemical preservation and the Horticulture Branch with its headquarters at Agra is 

entrusted with the laying out gardens and environmental development. 

Currently there are 116 ticketed monuments that exist in the 24 Circles. Based on available 

information for the year 2011, approximately over 40 million visitors have visited these 

monuments. The visitor history for these monuments is provided in Annexures 

(More details can be seen on ASI website, www.asi.nic.in) 



2. e-Ticketing Project 

2.1 Project Vision 

ASI proposes e-Ticketing initiative to harness the power of ICT Platform for its vision 

”To ensure transparent, easy, efficient ticketing system using ICT to facilitate world class 

Visitor experience” 

In order to streamline its processes and increase efficiency and effectiveness of services, ASI 

has undertaken a comprehensive exercise to implement ICT based e-Ticketing system across 

ticketed monuments across India. The ICT based system is also aimed to bring in 

transparency and sustainability of the processes. 

2.2 Project Overview 

ASI intends to establish a state of the art e ticketing solution which envisions the capability 

of the solution to sell and book tickets online and at the Point of Sale (POS) counters for 

the ticketed monuments using a centralized solution. The system should be hosted on a 

robust server which is capable of dealing on real time basis. The system should be able to 

generate tickets and validate the entry to the monuments. 

2.3 Project Objectives 

The key objectives of the e-Ticketing initiative are: 

a. Provide procurement of tickets through a web based centralized e ticketing solution 

with online payment facility 

b. Poide poueet of tikets at the Poit of “ale at ouets though a 

centralized e ticketing solution 

c. To increase the efficiency and improve monitoring and administration of ticketing 

d. To increase transparency and accountability to the ticketing system 

e. To improve visitor experience through issuance and validation of tickets 

electronically. 



3. Overview of Current State of Ticketing at the Monuments 

The section below detail the current state assessment of the processes being followed: 

ASI currently has multiple means of issuing tickets for monuments, most of which are Point 

of Sale based systems. Ticket issuance currently has the following typical characteristics: 

Tickets are typically printed centrally at India Security Press, Nasik, and issued to 

each circle based on indents received at the Headquarters. 

At each monument, the ticket issuing counters are usually separate from the ticket 

checking locations. 

Many monuments have multiple ticketing counters and multiple ticket checking 

entrances. A visitor could purchase a ticket from one counter and decide to enter 

from any of the ticket checking entrances, and vice versa. 

Tickets could be issued by multiple ticket issuers for the same monument, each of 

which could be a valid ticket format. 

Group bookings are possible, whereby a visitor could be issued multiple tickets for 

the same monument, each ticket being used for a separate visitor. A purchaser of 

ticket may therefore not necessarily be the end user of the ticket. 

Some tickets are available which provide a visitor access to multiple monuments on 

the same ticket. 

Usually, the ticket checking staff either collect the ticket altogether, or tear and 

retain a counterfoil with the stub being returned to the visitor. 

No mechanism exists to identify a ticket with a ticket holder either at the issuing 

point or at the checking point. 

The ticket issuers as well as the ticket checkers are typically Multi Task Support 

(MTS) staff members of ASI who are expected to perform this function in addition to 

their other routine functions. In many cases, this is not their primary job. 

There are no fool-proof mechanisms to ensure that only ticket holders enter a 

monument site. Likewise, there is no tracking mechanism to see whether every 

issued ticket is used at a monument site. 

The reconciliation of payments for tickets to issuance of tickets is currently manual. 

In many instances, registers are maintained to tally the amounts. Payments are not 

recorded in a system, and all deposits are made manually at the end of the day, at 

the local branch of the bank. 

In some cases, receipts are split between ASI and the local civic body with separate 

suissios to eah paties aks. 

3.1 Key problems being faced by different stakeholders 

It may not be out of place to mention here that the stakeholders who affect ticketing system 

in one way or the other face a lot of problems while delivering /receiving services. The key 



problems faced by ASI and different stakeholder groups are summarized in the following 

paragraphs. 

ASI 

No standard mechanism queue management at ticket counters and entry gates. 

Insufficiency of staff in manual ticketing process and deposit of funds in government 

account. 

Lack of effort to attend to complaints and grievances. 

Loss of revenue due to malpractices 

Citizens/Tourists 

Only single channel for providing the service, thus leading to Citizens standing in long 

queues. 

No priority ticketing for the elderly, women with small children and differentlyabled. 

Delay in closure of complaints and grievance redressal. 

Possibility of overcharging of visitor fee from the tourists visiting the monuments 



4. Project Requirements 

4.1 Statement of Work 

a. Study, design, customization, testing and deployment of a web-based e-ticketing system, 

integrated with payment gateway, to enable visitors to pre-book tickets on internet at 

their convenience. 

b. Supply, installation, configuration, customization, integration, testing and 

commissioning of Point-of-Sale (POS) application at ticketed monuments that shall have 

a common back-end platform that integrates with a common solution. 

c. Procurement, installation, configuration and commissioning of client side IT and non-IT 

infrastructure 

d. Deployment of server side application including IT and non-IT infrastructure at the DC- 

DR that is either owned by the IA or through a third party arrangement by IA. 

e. Facilitate ASI in provisioning, configuration and commissioning of network links to all the 

identified monument sites of ASI that enables connectivity to the Data Center and 

Disaster Recovery Center 

f. Supply of manpower services to manage and operate the ticketing system at ticket 

issuing counters and entry gates 

g. Operation and Maintenance of the entire e- Ticketing System including Application, IT & 

Non-IT infrastructure for a period of five years from the date of final Go-Live 

h. Documentation of the e- Ticketing Project 



4.2 Detailed Description of Requirements and Features 

4.2.1 Study, design, customization , testing and deployment of a web-based e-ticketing 

system, integrated with payment gateway, to enable visitors to pre-book tickets 

on internet at their convenience 

4.2.1.1 Detailed Functional Requirements, System Requirements Study and System Design: 

a. The Implementation Agency (IA) shall prepare an Integrated Project Plan for the 

entire project that covers detailed tasks which are intended to be performed, as part 

of the project. 

b. The roles and responsibilities for the project team along with support arrangements 

that are expected from ASI need to be jointly arrived at and have to be signed off 

between the IA and ASI. 

c. The IA needs to prepare and submit an Inception Report, which will serve as the 

foundation document for all activities related to the project. Additionally, the 

Inception Report must cover the risks the IA anticipates and the plans they propose 

towards mitigating those risks. 

d. The acceptance of the Inception Report by ASI is necessary before proceeding to the 

next stage of the project. 

4.2.1.2 Requirement Gathering and Analysis 

a. A high-level analysis of processes has already been done and functional 

requirements have been identified. The Functional Requirements as envisaged for 

this project is referred in Section 5 of this RFP. 

b. The IA needs to go through the document, and may consult with ASI wherever 

necessary to obtain more details on the requirements of the project and have to get 

a sign-off separately for the Functional Requirements. The IA shall conduct a detailed 

Functional Requirements gathering and prepare a Functional Requirement 

Specification (FRS) document. 

c. The IA shall conduct a comprehensive discussion with ASI (or its representatives) and 

subsequent analysis to ensure that each of the requirements captured in the FRS 

document is covered in the requirements analysis and are later captured in the e- 

Ticketing system. 

d. Atiities oduted as pat of this task ill esult i the pojet delieale e- 

Ticketing Functional Requirements specifications (FRS) & Software Requirement 

“peifiatios “‘“ douet, hih shall detail the euieets of the oplete 

solution up to the last possible detail. ` 



4.2.1.3 System Design 

a. Having conducted a comprehensive analysis of the requirements for the e-Ticketing 

system, the IA would need to prepare system architecture and design documents for 

the e-Ticketing project. 

b. The architecture document should give the complete architecture of the proposed e- 

Ticketing System. The documents including, but not limited to the following, shall be 

submitted for a sign-off. 

1. Application Functional architecture 

2. Format of all input screens including data entry requirements 

3. Format of all reports that would be generated by e-Ticketing System 

4. Access control mechanisms, data security and audit trails to ensure that 

databases are not tampered with or modified by unauthorized users 

c. Build a complete audit trail of all transactions (for e.g. add, update and delete) using 

transaction log reports, so that errors in data, intentional or otherwise, can be traced 

and reversed. Access Controls must be provided to ensure that the databases are not 

tampered with or modified by the system operators. Implement data security to 

allow for changes in technology and business needs. Based on the requirements 

analysis conducted above, the IA must develop a comprehensive solution for e- 

Ticketing system. 

d. Design and Implementation of the System Architecture: The Implementation Agency 

shall be entirely responsible for the architecture of the system implemented to 

satisfy all features, functions, performance and security as described in this 

document including sizing of the required hardware. System architecture description 

provided in this document is for reference only. The IA should ensure all possible and 

required improvements. 

e. The e-Ticketing system should be able to support all latest version of common 

browsers like Internet explorer, Mozilla, Chrome, Firefox, Safari etc. 

f. The IA shall oside uses iputs he the ae fializig all desig opoets 

including user interfaces, mode of data entry, storage and retrieval, outputs reports, 

queries and the application design as a whole. 

g. The IA shall prepare the Solution Architecture, Hardware Deployment Architecture, 

Network Design, Security Architecture etc. for the e-Ticketing system. 

h. The IA shall provide plans for User Acceptance Tests (UAT) and System Integration 

Tests (SIT) including Performance Tests (PT) to ASI and/or its designated Third Party 



Audit Agency (TPAA) and make the necessary changes to the e-Ticketing system to 

optimize performance. 

i. The IA would be responsible for making sure that all the above considerations are 

adequately met. The IA shall deliver an architecture document covering the above 

aspects. 

4.2.1.4 The IA shall deploy a dedicated team experienced in customization, testing and 

deployment of proposed e-Ticketing system portal. 

a. The IA shall ensure that the proposed e-ticketing portal provides adequate 

interfacing mechanisms (both at the application and data level) with a view to 

integrate with payment gateway systems. Such interfaces shall follow industry 

stadads suh as Appliatio Pogaig Itefae APIs ad e seies. 

b. The IA shall supply the application, database and related software, integration tools, 

along with the source code of customized function and requisite perpetual licenses 

for other software and tools. 

c. The IA shall create all necessary master files for the e-ticketing system. 

d. The IA shall design the hardware configuration in line with contemporary principles 

and ensure that it comprises various servers including database, application, web 

servers etc. 

4.2.2 Supply, installation, configuration, customization, integration, testing and 

commissioning of Point-of-Sale (POS) application at ticketed monuments that shall 

have a common back-end platform that integrates with a common solution 

a. Once the Solution Design Document (SDD) is completed and signed-off by the 

designated team of ASI, the IA shall procure and customize the POS application to 

implement the functional and design requirements as defined in the initiation phase. 

b. The IA should deploy a dedicated team experienced in customization, deployment of 

POS application as per the functional and technical requirements specified in the 

RFP. 

c. Configuring the POS application according to localization and specific requirements, 

development of interfaces where necessary. 

d. Provision of a desktop based and handheld based ticket issuance and verification 

application deployed at the monument sites. At every stage of the 

Customization/Configuration process, the different components of the e-ticketing 

system must get thoroughly tested to make it bug-free. 



4.2.3 Procurement, installation, configuration and commissioning of client side IT and 

non-IT infrastructure 

a. The IA shall draw out and provision the detailed specifications/requirements for the 

infrastructure that needs to be used for hosting the e-ticketing system including but 

not limited to servers, desktops, network equipment, application software, system 

software and any other software. 

b. The IA must procure, install and successfully commission the suggested hardware (as 

mentioned in the Client Side BOM covered under Section 7 of this volume) at all 

specified monument locations in such a way that the implementation plan does not 

suffer. 

c. The IA must install , configure and deploy the application on both POS hardware and 

handheld device 

d. Upon successful commissioning of all hardware and installing the software (both 

application software and system software), IA shall obtain a successful completion 

certificate from ASI. 

e. The IA must also procure and successfully install all the system software such as 

operating systems and any other software for using the e-ticketing system. 

IA is expected to prepare all project locations sites for setting up the 

necessary client site infrastructure. This will include but not limited to 

Provisioning Local area network (LAN cables, LAN ports, etc.) however civil 

works is excluded from the provisions, which shall be executed by ASI 

f. Supply of hardware, software, networking equipment, UPS to the location as per the 

requirements 

g. Physical Installation of Desktops, handheld device, ticket printer(s), Switch - 

Connecting peripherals, devices, Plugging in etc. 

h. Operating System Installation and Configuration 

i. Installation of Antivirus and other support software if any 

j. Configuring the security at the desktops and switches 

k. Network and application Configuration 



l. Test the accessibility and functionality of e-ticketing application from the desktops 

and handheld device 

m. Any other equipment that may be required and is proposed by IA in its proposal 

n. Ensuring all the systems required are supplied, installed, configured, tested and 

commissioned for declaring the site to be operational 

o. All hardware procured, shall be branded and reputed 

p. It must be noted that all system hardware and software shall be owned by ASI after 

delivery by IA. 

4.2.4 Deployment of server side application including IT and non-IT infrastructure at the 

DC-DR that is either owned by the IA or through a third party arrangement 

a. IA shall provide the facilities and services of a fully equipped Data Center (DC) and 

Disaster Recovery Center (DRC) meeting the specifications provided in Section 7.1 of 

this RFP volume I. The IA shall follow the best practices of Tier-3 and above norms of 

TIA 942 guidelines for the purpose. The IA shall provide such services from its own 

Data Center and Disaster Recovery Center or shall make arrangements for the same 

through tie-up with a third party. 

b. The IA shall consult ASI and/or its designated representatives before finalizing the 

sites for DC and DRC, with the proviso that the DC must be located in the National 

Capital Region (NCR) area. The IA shall ensure that adequate staff is available to 

operate and manage the DC and DRC at desired levels. 

c. ASI would provide the Quality of Service indicators and other performance 

parameters adequately in advance for the IA to study and make out detailed 

specifications for the same. The Specifications must be futuristic with at least a five 

year horizon to start with and recommended servers should be able to 

accommodate any scaling up requirements necessitated in future. 

d. Based on the recommendations, IA must procure, install and successfully 

commission the servers in such a way that the implementation plan does not suffer 



4.2.5 Facilitate ASI in Provisioning, configuration and commissioning of network links to 

the identified monument sites of ASI that enables connectivity to the Data Center 

and Disaster Recovery Center 

a. IA shall provision and commission two Network Connectivity links to all the specified 

monuments through Broadband connections of 2 Mbps each. The links provisioned 

have to be from two different service providers that enable connectivity to the Data 

Center and Disaster Recovery Center. 

b. The IA shall provision for internet gateway bandwidth at Data Center and Disaster 

Recovery Center for users who opt for internet ticket purchase, connecting to the eticketing 

system through dial-up/broadband to connect to the portal. For this 

purpose the IA shall arrange for a minimum of 10 Mbps bandwidth. 

c. IA shall also provision and commission 2 Mbps leased line replication links for 

connectivity between Data Center and Disaster Recovery Center from 2 different 

ISPs 

4.2.6 Supply of manpower services to manage and operate the ticketing system at ticket 


a. The IA shall supply manpower service provisioning for all the specified monuments 

for Point of Sale counters and ticket verification staff at entry gates as per the 

manpower requirement details. ( Refer to Annexure-3) The IA shall also maintain 

adequate no. of personnel at any given point of time for smooth implementation of 

operations throughout the project tenure. 

b. The IA shall also provide for an Operations Manager at World Heritage monument 

sites and Category A 

4.2.7 Operation and Maintenance of the entire e- Ticketing System including Application, 

IT & Non-IT infrastructure for a period of five years from the date of final Go-Live 

a. On successful completion of the implementation, the IA must extend Post 

Implementation Support (including warranty and AMC) till the end of contractual 

period which is 5 years from the agreed date of the project. 

b. The IA needs to provide the operational and maintenance support for the systems 

that are implemented and being used before Go-Live. The other details of 

operational support are provided in Section 8 of this RFP. 

c. The IA must provide centralized Technical Support for a period of 5 years from date 

of Fial Go Lie 

During the operational and maintenance support, the IA should: 



i. Ensure that all necessary measures are taken for the smooth operation of the e- 

ticketing system 

ii. Ensure that qualified persons from ASI support team are duly prepared and 

groomed in a progressive manner so as to operate the system on their own, with 

a view to eventually takeover operations at the end of contractual term 

iii. Ensure that all necessary know-how is transferred to ASI support team in an 

effective manner to facilitate a smooth transition. Performance metrics for the 

transition will need to be agreed between the IA and ASI. 

iv. Supply the consumables and any other goods or articles required from time to 

time for continued functional operations of e Ticketing system and at Monument 

sites : Consumables will include but not limited to 

a. Thermal Paper rolls 

b. Preprinted computer stationary 

c. Batteries for UPS 

4.2.8 Documentation of the e-Ticketing Project 

The IA must ensure that complete documentation of e-Ticketing system is provided with 

comprehensive user manuals, and adhere to standard methodologies in software 

development as per ISO standard and/or CMM models. The following documents are the 

minimum requirements: 

1. All Architecture documents, Design documents and, testing and deployment 

manuals etc. 

2. Quality Assurance Plan (not methodology) stating the planned actions to ensure 

satisfactory delivery conforming to functional and technical requirements of eticketing 

project. 

3. Test Plan containing information on the software test environment to be used for 

independent testing, the test cases to be performed, and the overall testing 

schedule. This includes, schedule, resources, tools, procedures, environment 

definition, test cases, and software test results. 

4. Operations Manual providing instructions for installing the application, 

troubleshooting, interpreting message logs, and FAQs (Frequently Asked Questions). 

5. User Manual (online or downloadable content) providing detailed instructions in the 

form of a narrative on how to use the software. In addition, it shall describe how to 

access, submit inputs to, and interpret outputs from the application. 

6. A data dictionary listing out all the data elements shall be prepared 

7. Operations Manual and FAQs fo uses ookig tikets olie though the potal . 



5. Functional Requirements - E-ticketing System 

The proposed e-ticketing system will meet the requirements of online booking by visitors 

and providing them ease of convenience. The e-ticketing solution will also integrate with 

Point of Sale (PoS) solutions which will be integrated so as to create an instantaneous record 

of tickets issued, and ensuring monitoring of the visitor traffic. The key functionalities of an 

e-ticketing solution include: 

5.1 Web based online ticket 

The implementation Agency (IA) is expected to build a platform which will integrate with 

A“Is eistig esite fo the iteet tiket ookig. The solutio should eale the isitos 

to book tickets online. 

5.1.1 Foreign Visitors 

1. The system shall allow relevant data like name , nationality, passport no., email Id, 

no. of visitors, etc. to be captured for issuance of internet ticket 

2. The system shall also allow data such as Date, No. of Monuments. For example the 

system shall allow to book for multiple monuments 

3. The system will allow ticket booking for multiple monuments within one circle only 

at a time 

4. The system should also capture details of differently abled visitor requirements for 

instance , wheelchair services where available 

5. The system should send email alerts regarding booking details 

6. The printed internet ticket will have all data captured during the time of booking 

7. The system should send email alerts to visitors who have booked earlier on special 

exigencies such as bandh, security threats, VIP visits etc. 

8. The system should allow the visitor to take a print out of the ticket at the time of 

booking or enable printing of ticket at users convenience. 

9. The system should allow currency converter 

10. The ticket should support verification / authentication feature i.e. barcode 

11. The system should allow integration with payment gateways 

12. The system should also allow integration with other service providers to provide 

value added services 

13. The interface should provide web helpdesk for any visitor queries, grievances etc. 

The system will not allow ticket booking where the monuments have been closed 

temporarily due to reasons such as preservation, security etc. where applicable 

14. The system will allow configuration of ticket validity period 



5.1.2 Indian Visitors 

1. The system shall allow relevant data like name , email Id, no. of visitors, etc. to be 

captured for issuance of internet ticket 

2. The system shall also allow data such as Date, No. of Monuments. For example the 

system shall allow to book for multiple monuments 

3. The system will allow ticket booking for multiple monuments within one circle only 

at a time 

4. The system should also capture details of differently abled visitor requirements for 

instance, wheelchair services where available 

5. The system should send an email / SMS alerts regarding booking details 

6. The printed internet ticket will have all data captured during the time of booking 

7. The system should send email / SMS alerts to visitors who have booked earlier on 

special exigencies such as bandh, security threats, VIP visitors, etc. 

8. The system should allow the visitor to take print out of the ticket at the time of 

booking or enable printing of ticket at users convenience. 

9. The ticket should support verification / authentication feature i.e. barcode 

10. The system should allow integration with payment gateways 

11. The system should also allow integration with other service providers to provide 

value added services 

12. The interface should provide web helpdesk for any visitor queries, grievances etc. 

13. All screens and templates of the system should be in English and support Devanagari 

script where required.. 

14. The system will not allow ticket booking where the monuments have been closed 

temporarily due to reasons such as preservation, security etc. where applicable 

15. The system will allow configuration of ticket validity period 

16. All special cases such as school historical visits etc. will be issued Authorization / 

Entry pass however with data captured such as date, time, monument, no. of 

children, etc. ( Upto 15 years only) and the system will reconcile the numbers in the 

central database 

17. All special cases such as school historical visits etc. will be issued tickets with data 

captured such as date, time, monument, no. of children, etc. ( above 15 years) with 

total value of ticket printed on the entry ticket and the system to reconcile the 

numbers in the central database 

18. Special cases such as freedom fighters etc. will also be issued Authorization / Entry 

pass with data captured such as date, time, monument, no. of visitors etc. and the 

system will reconcile the numbers in the central database 

19. “peial ases suh as VIPs ad suh digitaies ill also e issued Authorization / 

Entry pass with data captured such as date, time, monument, no. of visitors etc. and 

the system will reconcile the numbers and the details in the central database 



20. The System should generate an entry pass / authorization letter for School Groups, 

VIP ad VVIPs etc. 

5.2 Tickets Sale at the counter / Point Of Sale (for Walk In Visitors) 

1. Tickets issued over the counter/POS at the monuments will be issued through a 

central database which is integrated with the internet ticketing system(I –Ticket) 

2. The system should be able to automatically sync with the central system with regular 

updates 

3. The system should be able to generate tickets in an offline mode 

4. The system should enable ticket issuance by either a PC or a hand held device 

5.2.1 Foreign Visitors 

1. The system should enable issuance of e ticket over the counter 

2. Provision for payment through cash in Indian currency only 

3. Provision to pay using Credit cards / Debit cards 

4. Counter ticket issued will have data captured such as time, date, monument, issued 

by, during the time of booking 

5. The system should allow validation and authentication of tickets at the ticket 

checking counters at monument/sites 

6. The ticket issued over the counter should support verification / authentication 

feature through barcode 

5.2.2 Indian Visitors 

1. The system should enable issuance of e-ticket over the counter 

2. The system will keep provision for cash payment only 

3. The system will capture date, time, monument, issued by and no. of visitors 

4. The over the counter ticket issued will have data captured such as time, date, 

monument, issued by, no. of visitors (no. of adults and no. of children), type of 

visitors during the time of booking 

5. The system should allow validation and authentication of tickets at the ticket 

checking counters at monument sites 

6. The ticket issued over the counter should support verification / authentication 

feature for i.e. barcode 

5.2.3 Validation / Authentication 

1. All tickets issued whether through internet or through the POS will have to be 

validated and authenticated by the system ( For Example- Barcode) 

2. All visitor tickets that are authenticated by the system shall secure access to the 

monument. 



3. The system should be capable to carry out a real time validation with the central/ 

local system. 

4. The system should be capable of invalidating the ticket once it has been 

authenticated at the entry gates 

5. The ticketing checking staff shall have to verify the ticket and the system shall 

validate the entry 

Group Booking – Online 

1. The system should be able to allow group bookings over the web 

2. The system should allow upto 25 persons in one single purchase 

3. The system should capture all information about the buyer 

4. The system should generate barcode for 25 tickets for verification 

Group booking – POS 

1. The system should be able to allow group bookings over the POS 

2. The system should allow upto 10 persons in one single purchase 

3. The system should generate barcode for 10 tickets for verification 

5.3 General 

1. The system should generate MIS reports including ticket use and usage status, 

revenues, non-issue, or incomplete transactions, etc. 

2. The system should have ticketing performance management dashboard for ASI 

Headquarter to monitor 

3. The IA should provide a helpdesk interface integrated with the e-ticketing solution to 

handle queries. 

4. To meet the requirements, the IA should provide an e-ticketing solution customized 

to meet the convenience of foreigners and Indian tourists. 

5. The e-ticketing solution should be built on scalable hardware and available solutions 

so that scalability can be achieved, in terms of the volume of users and services it 

can support concurrently, therefore it must have capabilities to operate with an 

estimated daily peak load of up to 300,000 purchases per day. The web-ticketing 

solutions must be able to authenticate whether the purchaser is Indian or foreign 

and should issue tickets accordingly. 



5.4 Non-functional requirements: 

1. The solution should be able to dispense tickets even without internet connectivity, 

with a feature to store information locally and upload to the centralized database on 

availability of internet connection. 

2. The PoS component of the solution should consist of a manned counter, where 

tickets are issued by an issuer based on information provided verbally by the 

purchaser. 

3. Adequate authentication methods must be built in to prevent revenue leakages. At 

the PoS, tickets would be printed and issued by the ticket issuer. 

4. Power and internet connectivity: The PoS solutions would have adequate provision 

for back-up power to enable uninterrupted functioning for sunrise to sunset in a day. 

5. The IA has to manage end to end ticketing operations (which includes, online 

ticketing, payment gateway, ticket issuance at POS, ticket validation, reconciliation 

of collections etc.) 

6. Each of these solutions should have a common back-end and integrate with a 

common solution. Further, the ticket available for verification at the Monument 

gates should have a common and easily recognizable format. 

7. There will be a separate checking queue for Internet ticket holders and a separate 

queue for POS ticket holders to validate the tickets of visitors 



6. Technical Architecture & Requirements 

The IA shall deploy/ implement the e-Ticketing system with all the necessary functional, 

technical, operational and other supporting requirements. 

6.1 Technical Requirements 

The e-ticketing solution will provide for the following technical requirements: 

i. Browser support on multiple browsers for online users. 

ii. An interactive and easy to use GUI interface for the operators and online users. 

iii. An integrated interface for the Technical Support 

iv. For PoS locations, the solution should support low bandwidth. In certain cases, there 

might not be any connectivity available always, hence the proposed solution should 

have ability to also work offline and synch data as and when connectivity becomes 

available. 

v. For PoS locations, the solution should also support batch processing and uploads, as 

a contingency arrangement. 

vi. Secure electronic payment gateways integrated with the e-ticketing solution, which 

are enabled for most commonly used electronic payment options, including direct 

payment through Net banking, credit and debit cards 

vii. The system should support open standards 

viii. The interface should provide self-learning kits, FAQs use guides et. to use the 

system 

ix. The interface should provide web helpdesk for any visitor queries, grievances etc. 

x. The IA should provide technical support for any technical glitches 



Indicative E-Ticketing Solution Architecture 

Ticket Printer 

Ticket Issuer 

Barcode Reader 

Ticket Verifier 

POS 

User 

Interface 

Ticket Verification 

Interface 

Printer Offline Online 

UI 

Framework 

Integration Gateway 

Business 

Rules for UI 

Rendering 

Logging Framework, Standads, Security 

Ticket 

Validation 

Component 

POS 

Internet 

Barcode Online Offline 


Business 

Rules 

Logging, Auditing, Standards 

Ticket Validation 

Figure 1: Indicative Solution Architecture 

Internet 

Data 

Synchronizer 

Data 

Synchronizer 

Local 

Database 

Interface 

Local DB 

Email SMS 


Ticketing 

Framework 

Business 

Rules 

Payment 

Gateway 

Archeological Survey of India, Ministry of Culture Page 29 of 107 

Agent 

Interface 

Online 

Portal 

POS 

Interface 

Mobile 

Interface 

Admin 

Portal 

Admin 

Reports Configuration 

Database 

Framework 

Logging, Auditing, Standards 

Holiday 

Management 

Monitoring Management, MIS Reports 

Security, Authentication, Authorization etc. 

Application Layer (Web + logic) 

Handheld Device User Online User 

The description (text, pictures, figures, and diagrams) of requirements given in the RFP is 

for providing as detailed an understanding as may be required for bidders to prepare their 

proposals and should not be construed as comprehensive. The requirements will have to 

be detailed further during SRS in order to design the system. 

Channels 

Access Channels define the interface between an application and its users, whether it is a 

browser, mail or any other medium. The e-ticketing application should be designed to book 

tickets using various channels such as Point of Sale, Hand held Device and through online 

portal. The user interface layer shall correspond to the different interface channels required for 

DB Node1 

DB Node2 

Database 

Layer


different roles such as Admin interface, mobile user interface, POS interface and ticket verifier agent 

interface. 

User Administration 

The application administrator should be able to add new users, groups, etc. into the system. 

Assignment of roles to these users and group shall be done in this module. Various roles 

that shall be configured and supported in the application are Super Administrator, 

Administrator, ASI Manager, Ticket issuer, Ticket verifier, online user and mobile user. 

Adding new roles should not impact the current roles and their behavior. However the user 

management and role-rights assignment should be exposed only to super administrator 

profile user. 

Authentication and Authorization 

Security is the critical component of the solution architecture which shall be implemented 

through Single User ID along with role based access control for e-ticketing system modules. 

Security layer components should adhere to the standards for the security management as 

prescribed in this volume of the RFP.The Application users shall be authenticated using the 

security module that is designed to support Lightweight Directory Access Protocol (LDAP) or 

Database for identity storage and authentication. The system shall support Role Based 

Access Control (RBAC) at Web Application level and user interface level. 

Presentation Layer 

The communication between e-ticketing framework and the actors that communicate with 

e-ticketing system is performed via Web Services. The presentation layer components 

extract the data from the services and presents to the user in a personalized format. When a 

user places any service request, these service interfaces invoke the respective applications 

and data returned by the application and presented to the user in a readable format. 


The IA shall use A“Is eistig gatea seies to the etet possile to itegate seies 

such as Email to send out alerts and notifications to the visitors utilizing online ticket 

booking services. The online users will receive an e-mail notification with the booking 

number after successful booking. Therefore the administrator user should be able to notify 

users if there is any unplanned activity which forces the monument to be closed for any 

particular day. 

IA will have to develop the required interfaces for user and business layer to get integrated 

to SMS and Payment. Payment gateway integration should be simple and flexible. Changing 

the payment gateway vendos shouldt ipat the appliatio. The paet gatea 

interface shall be accessed through a secure communication HTTPS protocol. IA shall 

procure, install and implement the SSL Web Server certificates for online security. 



Interfacing Requirements: 

The e-ticketing solution should interface with the multiple payment gateways authorized by 

ASI. The solution shall support card payments using all the popular debit and credit cards 

(Visa, Master Card etc.) and Net Banking. The solution must also have interface with 

electronic card reading solutions such as barcodes. 

The IA shall also develop interfaces for the seamless working of e-ticketing application with 

various devices used for ticket printing and verifying operations. 

Business Services Layer 

This layer basically consists of actual modules of the system in the e-enabled scenario. 

Conceptually, the system can be conceived as a synthesis of inter-linked modules for the 

A“Is e-ticketing business area. System shall also enable authorized users to define business 

rules. 

The ETS modules shall comprise of: 

1. Administration module for user creation, granting role rights to the 

authorized users of the ETS system functions, password management etc. 

2. Electronic Ticketing System (ETS) Front Office Portal user module for ticketing 

services to foreigner/ Indian visitors, travel agents, school bookings, 

government functionaries. 

3. Point of Sale (POS) desktop user module: This module shall be used by both 

ticket issuers and ticket verifier for their respective functions 

Reports module: This module shall provide host of reports and MIS regarding the ticketing 

functions whether online ticketing or point of sale. This shall be used by the authorized 

users of the organization. 

Data Synchronizer: 

The Ticket Generation and Printing at Point of Sale should be done online only. In case of no 

connectivity, the booking office should be able to issue offline tickets with a barcode. The 

tickets printed in exception cases shall be stored in a local database that shall be later 

synchronized with the centralized database. The validation application should also have 

access to these exception ticket numbers that are generated locally for the monument. 

Therefore every inbound and outbound synch should be supported at Validation Station. 

Logging, Auditing and Standards: System should have audit logging capability to record 

access activity of all the transactions. Policy and guidelines are the guiding principles for 

the overall e-Ticketing system architecture. Any component envisaged should strictly adhere 



to the policies and guidelines laid out by ASI. The e-ticketing system solution shall follow 

open standards and other technology standards. ( Add Policy document as Annexure) 

Management, Monitoring and MIS Reports 

IA will provide availability and performance reports for the equipment installed in the DC-DR 

along with system resources at the monument sites. The IA should ensure that necessary 

reports are generated and SLA requirements are met. The monitoring and management 

should not result in procurement of a high end solution with large number of servers. 

Various reports (Live and Historical) should be available to the authorized users of ASI 

management. MIS reporting requirements specific to ticket issuance and checking activities 

shall include providing graphical views for information such as: collections for each 

monument, statistical/trend view (rate of growth of transactions and predictive growth of 

transactions), historical view (collections till date). 

The following are indicative reporting requirements that the IA should take into account 

while designing an appropriate solution: 

i. Ticket type-wise Hourly/Daily/Weekly/Monthly transactions/collections by 

monument 

ii. Day wise transaction & collection summary reports by monument 

iii. Ticket type wise transaction & collection summary for the day reports by monument 

iv. Counter-wise transaction, and collection report for the day at a monument 

v. Cash collections report to be submitted end of business each day, along with the 

handover of cash 

vi. Distribution of load across all the counters for the day 

vii. Transaction & Collection summary report for all ticketed monuments of ASI 

viii. Service-wise Transaction & Collection summary report for all centres 

ix. Centre wise payment-mode wise collection reports 

x. Arrival pattern of walk-in applicants over different hours of the day 

xi. Graphical reports for providing a trend analysis of above statistics (as applicable) 

xii. Validation Reports: Invalid Ticket Report, Duplicate Ticket Reports 

xiii. Revenue Reports: Hourly Report/ Monthly Report/ Revenue by Monument/ Revenue 

by Circle/ Revenue by Country Category/ Revenue by POS vs Online. 

Monitoring 

i. Apart from the SLA monitoring the IA, should provide the monitoring statistics of 

Application Server (Response Times, API Calls to ticket generation component, life 

cycle calls, server uptime statistics, system resource usage statistics etc.) using a 

standard Monitoring tool. 



ii. IA on a pre-defined time interval should provide to ASI the monitoring statistics of 

Database Server (including but not limited to statistics on CPU, Memory, Database 

growth patterns) 

iii. The following application specific reports should be available to the ASI management 

apart from other technical reports/ statistics: 

a. POS (Active, Inactive) Reports 

b. User Login Audit Reports 

c. Validation failure reports 

d. Monuments in which invalid tickets are found frequently. 

Application architecture 

The E-Ticketing System (ETS) application shall comprise of a Centralized Database. The 

Application should be designed with open standards and extensible framework. 

i. Cetalized Dataase shall be hosted at the Data Centre and Disaster Recovery 

Center and accessed through the web interface. 

ii. Each of these ETS applications will consist of Sub applications. For example POS 

application, Verifier application, Mobile application etc. that shall be locally installed 

at the POS terminals/ hand held devices. These applications shall essentially be a 

web-based application configured to store data centrally and also have capability to 

store and push data to central database in case of no connectivity. The POS 

application must be desktop based application. 

iii. Should be built based on open system architecture 

iv. Should be easily customizable to accommodate changes in laws, regulations, best 

practices and new technology 

v. Critical Data such as Transaction Logs, and Database data should be stored in SAN 

storage. IA shall design the architecture in such a way that the application should not 

fail because of data unavailability. 

vi. Separate Report server should be designed and made accessible to authorized user 

groups 

vii. Online Booking application should be deployed in a separate cluster. Since the 

availability is close to 100%, it requires separate instances. 

viii. The IA shall also plan for an archival database. Last one year data should be available 

in the main database and the rest of the data should be moved to archival database. 

This should be done by using automated scripts. System should have internal 

transaction processing controls , including the capability in the event of system 

failure, to automatically: 

a. Roll Back incomplete transactions 

b. Restore the system to its last consistent state before the failure occurred 



c. Reapply all incomplete transactions previously submitted by the user 

d. Internal database consistency during all online and batch operations. 

e. System shall include an integrated relational, structured query language 

compliant database 

f. Should be capable of simultaneously processing online transactions and 

transactions submitted via system interface. 

Application-related Technical features 

Application Solution must be web enabled with sufficient flexibility for customization 

ased o A“Is eeds 

Solution must use standard relational database. 

Language Support: All functionality must provide support for the English language. 

All the screens and templates should be in English. Where required, screen shall 

support Devnagri script. In addition application shall support Unicode formats for 

text editing, file name, data storage. 

Dates: All functionality MUST properly display, calculate, and transmit date data, in 

21st-Century date data (DDMMYYYY) format. 

Application and other standards 

This section details the various Information Technology (IT) related standards that are to be 

considered while developing the e-Ticketing system. The below mentioned components 

need to be taken care of while developing the technology components on e-Ticketing: 

Platform Flexibility 

i. Web-centric, multi-tier architecture shall be used 

ii. Open Standards and Interoperability shall be used 

iii. XML based standard shall be used wherever applicable 

iv. Compliance to SOA and Web-services 

Interoperability 

i. Usage of standard APIs 

ii. Service-oriented architecture (SOA) based 

iii. Support for multiple industry standard databases with ODBC, JDBC and Unicode 

compliance 

Usability 

Applications should comply with Guidelines for Indian Government Websites 



Scalability 

All the components of the DC-DR physical architecture must support scaling-up 

requirements in order to meet future growth and IA shall propose an optimum solution 

keeping in view the trends at present. 

The system must be able to handle a minimum load of 5 crore tickets (Please refer to 

Annexure) on a year to year basis. Therefore the IA is expected to plan and provide for 

horizontal scalability in such a manner that a new server can be added (or removed) 

dynamically, as and when required in future, without disturbing the normal functioning of 

production system. The vertical scalability in servers in terms of additional processors and 

RAM will have to be provided for handling future growth in transactions. 

IA shall plan the exact requirements for SAN storage keeping in view the ticket volume 

trends that needs to be stored IA shall make an independent assessment of the requirement 

and propose a SAN solution accordingly. 

Availability and Redundancy 

While designing the physical infrastructure setup at DC and DR IA shall plan and consider 

redundancy for all the active and critical server components. Redundancy is required to 

provide maximum uptime and ensure that no single point of failure (SPOF) exists and 

enough redundancy is built in the DC-DR setup. 

Manageability 

IA must plan for Ease of configuration, on-going health monitoring and failure detection are 

vital to the goals of scalability, availability, and security so as to match the growth of the 

environment. 

Security 

The bidder must provide an end-to-end security model that protects data and the 

infrastructure from malicious attacks, theft, natural disasters etc. For server security, the IA 

shall on an ongoing basis perform Vulnerability Assessment of the Server, perform server 

hardening and provide additional Layer of Security to applications by deploying these 

behind the Firewalls. 

Security Requirements and features 

The implementation agency will have to establish all the necessary procedures / 

infrastructure/ technology / personnel to ensure that the e-Ticketing system Security is not 

compromised. 



Broad Security requirements are: 

Security features should be compliant with the e-Governance Security Guidelines (e Gov 

Security Standards Framework). 

i. All systems should have integrated security features that are configurable by the 

system administrator to control access to the application, functional modules, 

transactions, and data. 

ii. The applications should require the use of unique user IDs and passwords for 

authentication purposes. 

iii. The application should allow for the following: 

a. The enforcement of password standards 

b. The establishment of a specified period for password expiration, and 

c. The prohibition of recent password reuse 

iv. System administrator should be able to define functional access rights and data 

access rights by assigned user ID, functional role, and owner organization. 

v. The systems should permit the system administrator to assign multiple levels of 

rights to a single user. 

vi. System administrator should be able to restrict access to sensitive data elements by 

named user, groups of users, or functional role. 

vii. System should be auditable as per requirements from time to time. 

viii. System should have audit logging capability to record access activity, including the 

following: 

a. All log-in/log-out attempts by user and workstation; 

b. User-submitted transactions; 

c. Initiated processes; 

d. System override events; and direct additions, changes, or deletions to 

application-maintained data 

ix. System should provide the ability to query the audit log by type of access, date and 

time stamp range, user ID, or terminal ID. 

x. All the information assets (information and information systems) should be classified 

and security should be defined according to criticality of the information asset. All 

the data / information contained within systems or in hard copies related to this 

project, are owned by ASI. No information should be made public either directly or 

indirectly nor allowed to be accessed by an unauthorized person. 

xi. System audit should be enabled for all the information assets to establish detective 

controls. System should have evidences, like audit trails, logs, registers, proof of 

background checks, approvals from ASI or its designated agency, support for various 

decisions, support for accounts etc. for the purpose of third party security audit. 



xii. System should have security incident management procedures. This incident 

management procedure has to use Technical Support facilities and should be 

reported in the incident management System. 

xiii. Should have system development and change control procedures including effective 

segregation of duties and environment. 

xiv. Proper protection against malicious software should be ensured. This would include 

implementation of an effective anti-virus solution, scanning viruses at regular 

intervals or on certain triggers and updating the solution as and when new patch is 

received from the anti-virus solution provider. 

xv. Should have proper logical access security for all the information assets. Entire 

network including servers, communication links, database etc., should be logically 

segregated from rest of the networks. 

xvi. Should ensure suitable technical and procedural controls to protect the network. 

Wherever the e-Ticketing project network comes in contact with an untrusted 

network, additional security measures should be taken like firewall, IDS, DMZ, proxy 

server, encryption etc. 

xvii. Should have a business continuity plan and a disaster recovery plan that should be 

implemented before commencement of the operations. Robust backup procedures 

should be established for the same. 

xviii. Vulnerability Assessment of the Servers shall be carried out 

xix. Servers shall be hardened regularly 

Compliance with Industry Standards 

The Solution shall be based on and compliant with industry standards (their latest versions 

as on date) wherever applicable. This will apply to all the aspects of solution including but 

not limited to design, development, security, installation, and testing. There are many 

standards that are indicated throughout this volume as well as summarized below. However 

the list below is just for reference and is not to be treated as exhaustive. 

Information access/ transfer protocols SOAP, HTTP/HTTPS 

Interoperability Web Services, Open standards 

Information Security System to be ISO27001 compliant 

Operational integrity & security 

management 

System to be ISO17799 compliant 

IT Infrastructure management ITIL / EITM specifications 



Service Management ISO 20000specifications 

Project Documentation IEEE/ISO specifications for documentation 

Internet Protocol IPv6 ready equipments 

Barcode Verifier ISO /IEC 15426-1(Linear) or ISO /IEC 15426- 

2 

Printers Should support ID barcodes(Code 39, Code 

128 A,B,C) & 2D Barcodes ( MaxiCode,QR 

Code, Data Matrix, Composite Code) 

Table 2 : e-Ticketing System Standards 

The system shall adhere to all the standards published by the Department of Information 

Technology, Government of India. (www.deity.gov.in) 

Audit Requirements 

ASI may undertake an exercise of Audit and Certification of e-Ticketing system through a 

third party, after the completion of system implementation. The following methodology will 

be adopted by the IA: 

i. IA shall host only the pre-audited and certified, defect-free 

application/upgrades/patches at its Data Center/ Disaster Recovery Centre. 

ii. ASI shall nominate a suitable, neutral and technically competent third party agency 

or agencies for conducting audit and certification, upon intimation by the IA that the 

system implementation is complete. 

iii. The system shall be audited through a CERT-in enrolled audit agency. ASI shall pay 

for the Third Party Audit. 

iv. The agencies nominated by ASI shall establish appropriate processes for notifying 

the IA of any deviations from the norms, standards or guidelines at the earliest 

instance, after noticing the same, to enable the IA to take corrective action. 

v. Such an involvement and guidance by the agencies shall not, however, absolve the IA 

of the fundamental responsibility of designing, developing, installing, testing and 

commissioning the various components of the e-Ticketing project to deliver the 

services in conformity with the RFP, SLA and the agreement. 

vi. All changes suggested by the audit agency shall be implemented by the IA upon 

acceptance and approval by ASI. 

i. The IA shall extend all support to ASI nominated Third Party Audit Agency (TPAA) 

for all the activities related to audit and certification. 



ii. The IA shall also provide access to ASI and TPAA to audit its facility for the 

purpose of smooth conduct of audit and certification of e-Ticketing project. 

iii. IA shall share with TPAA test plan, test cases and equipment including requisite 

test environment and test data at its facility for the smooth conduct of testing 

(including but not limited to functionality testing of online system and POS 

system security, performance, infrastructure audit etc.) audit and certification. 

iv. After the user acceptance test of the e-Ticketing system and its audit certification 

by TPAA. ASI shall have the complete discretion to ask IA to rollout the system. 



7. Infrastructure Requirements 

7.1. Data Centre and Disaster Recovery Center requirements 

The following section presents the specifications for the data center hosting the e-Ticketing 

system application. 

These specifications are required to be fulfilled as a minimum and the bidders are expected 

to make their own assessment with respect to exact requirements and formulate their 

proposals accordingly. 

A disaster recovery infrastructure shall be established commensurate with the need, to 

ensure minimum data loss in the event of failure of primary data center. It shall be equipped 

to the extent required. 

The data center and disaster recovery center shall be in two different cities and shall be 

finalized in consultation with and on approval of ASI. 

The IA must adhere to the best practices of Tier-3 and above norms of TIA 942 guidelines for 

setting up DC and DRC. 

An indicative list of various hardware and software components that will have to be 

provided by the IA is provided below. The list is not exhaustive and bidders are required to 

assess the actual requirement and arrive at an optimum list. 

1. Application and storage hardware 

a. Web Server 

b. Authentication Server 

c. Application Server 

d. Database Server 

2. Network Connectivity 

a. WAN Connectivity at internet gateway 

b. Replication Links between Data Center and Disaster Recovery 

3. Software 

a. Web server software 

b. Application server software 

c. Database server software 

d. Enterprise antivirus system 

e. Relevant EMS for SLA measurement tools and application monitoring for only 

those resources that are provided by IA 

4. DC and DR Services 

a. Routers 

b. Core Switches 

c. Access Switches 



d. Server farm Switches 

e. IPS/ Firewall & Enterprise Anti Virus 

f. Back-up software 

g. Enterprise Management System for Server availability and network monitoring 

and management (as a shared DC-DR rental service) 

h. Management & Monitoring servers 

i. SAN Storage system (including switches) 

j. Load Balancers 

IA will provide availability and performance reports for the equipment installed in the DC-DR 

along with other resources as listed above. IA should ensure that necessary reports are 

generated and SLA requirements are met. The monitoring and management servers should 

not result in procurement of a high end solution with large number of servers. The 

assessment of the actual number and configuration of the components mentioned above 

would be done by IA keeping in view that none of the functional, non-functional, technical, 

operational, and service level requirements laid down in the RFP is compromised. 

Client Side Bill of Material 

The following section presents an indicative requirement of Client side Infrastructure for 

POS systems. 

Ticket issuing counters: 

The following section presents the requirement for the e-Ticketing system application. 

These specifications are required to be fulfilled as a minimum and the bidders are expected 

to make their own assessment with respect to exact requirements and formulate their 

proposals accordingly. 

ASI will provide space for ticket issuance counter(s) but IA will be responsible for its set-up. 

The broad requirements with respect to ticket issuance counter are as indicated below: 

a. Desktop PC for counters at the POS 

b. Handheld device along with charging units 

c. Printers for counters for scheduling the print jobs 

d. Currency chest for the cash collected at Point of Sale (POS) 

e. One Currency counting and one fake currency detection machine in World Heritage 

Monuments, Category A & B monuments 

f. Wireless / Wired LAN for connecting all PCs, printers and other IT components for 

World Heritage , Category A & B monuments 

g. Network components for LAN connectivity and connectivity with DC and DRC 

h. Connectivity with DC and DRC 

i. UPS back up for all equipments / components (IT & non IT) participating in printing 

process, all lights and fans 



j. Operators for handling the printing and other related jobs 

k. One Drop Box for collection of visitor feedback, with adequate number of preprinted 

feedback form stationary 

l. Installation and configuration of Operating System, antivirus any other support 

software for desktops and handheld device 

m. Supply of consumables and any other goods or articles required from time to time 

for continued functional operations of Point of Sale. 

The above are indicative requirements and more detail for these will have to be gathered 

by IA during the SRS stage. 

Ticket checking/ Ticket entry: 

The IA shall also be responsible to deploy ticket checking staff at the identified ticketed 

monuments. For ensuring smooth operations of the entire ticket issuance and checking, the 

IA shall deploy an Operations Manager in category A monuments who shall be responsible 

for crowd management and will also provide grievance redressal to visitors. 

ASI will provide space to IA for set-up of IT equipment required for ticket checking 

counter(s), but IA will be responsible for its set-up. The broad requirements with respect to 

ticket checking counter(s) are as indicated below: 

a. Multiple no. of bar code readers/scanners 

b. Network components for LAN connectivity 

c. Connectivity with DC and DRC 

d. Operators for handling the barcode reader(s)/scanner(s) and other related jobs 

e. The IA shall maintain the adequate stocks of spares to meet the requirements. The 

monument Incharge shall reserve the right to verify the stocks at any time. 

f. Supply of consumables and any other goods or articles required from time to time 

for continued functional operations of checking/validation counter. 



7.2. Network connectivity 

Disaster Recovery 

Site 

2Mbps Secondary link from ISP2 

WAN Connectivity 

(Broadband) 

Intranet (Broadband) 

Replication Links 

2Mbps Primary Link 

2Mbps Secondary Link 

10 Mbps Gateway Bandwidth 

2Mbps Primary link from ISP1 

Data Center Site 

DR Intranet Router DR Internet Router DC Intranet Router DC Internet Router 

Ticketed Monuments 

Figure 2: Network Diagram 

7.3. 

10 Mbps Gateway Bandwidth 


Internet 

Foreign Visitors 

Indian Visitors 

Travel Agents 

The following table presents the network links and bandwidth requirements for the 

proposed network: 

# Network Link Locations/Connectivity Bandwidth Size 

(Minimum) 

1. N1 ASI monument sites 2Mbps Broadband 

connectivity to DC and 

DR (Primary from ISP 1 

and Secondary from ISP 

2) 

links 

2. N2 Leased Line Links for 2 Mbps Leased 

Data center and 


connectivity for 

replication (Primary link 

from ISP1 and 

Secondary link from 

Line Links 

Provided by 

IA 

IA 

Dial up/ 

Broadband 

Leased line


ISP2) 

3. N3 Internet connectivity for 

Data Center and 


Table 3 Bandwidth requirement 

10 Mbps IA 

The above is an indicative bandwidth requirement for ASI office connectivity, which will 

have to be studied and finalized by the IA in consultation with ASI during the SRS stage. 



8. Operational Requirements 

Performance Requirements 

The number of Monuments and approximate footfalls figures are given in the Annexure. The 

actual requirement of support will be ascertained by IA during implementation. 

a. The average application response time(s), application availability and other 

performance parameters are given in the SLAs of Volume-III of this RFP. 

b. The application software should be designed to cater to the visitor load without any 

degradation of performance as explained above. 

c. The database schema and design should be capable of handling current and future 

loads. 

d. System should be upwardly scalable in the event of increased usage of the system or 

new business requirements. 

e. The IA shall provide comprehensive report every month on the performance of the 

server side infrastructure and client side infrastructure 

f. The IA shall provide comprehensive report every month on the performance of the 

operations of ticketing such as Manpower, Grievances etc. 

g. ASI may with prior notice audit such measurements as pe defied “LAs . 

h. The application should be able to process the ticket validation and generation 

activities in parallel 

Support Requirements 

The IA shall provide Operation and maintenance (O&M) support to ASI for 5 years from the 

date of oplete Final Go-Lie of the E Ticketing system (ETS). The IA will provide post 

implementation support for Five years after acceptance of Final Round Go-live. 

The support will address all user level queries, fixing bugs, enhancements, changes to 

configurations, customizations, patch updates, upgrades, database administration, security 

etc. During Post Go- Live support, the IA will conduct the Stabilization Test for the e 

ticketing solution as defined in this document. The Operation & Maintenance of the Overall 

System Solution (including but not limited to Hardware, System Software, Application Software 

and other Infrastructure) shall be for a period of 5 Years fo Final Go-Lie. 

Operation & Maintenance of Application Software and infrastructure for a period of 5 years 

from Final Go-Live 

1. Compliance to the Functional & Technical Requirements 

2. Compliance to SLA 

3. Application Software Maintenance, Problem identification and Resolution 

4. Software Change & Version Control as per industry standards 



5. IT and non IT Infrastructure Operations and Maintenance as per Standards for a 

period of 5 years from Final Go-Live. 

6. Other infrastructure operations and maintenance in compliance to Service Level 

speified i ‘FP fo a peiod of Yeas fo Final Go-Lie 

Ensure the following from OEM for the equipment supplied: 

I. Commitment of support for spares and services for a period of 5 years from the date of 

Supply from OEM 

II. “ste adiistatio ad dataase adiistatio of appliatio fo eas fo Final 

Go-Lie. 

III. Implement a SLA monitoring tool in consultation with Project Operations Committee 

(POC) and Project Monitoring Unit (PMU) for SLA Monitoring during O&M Phase. 

IV. Provisioning of Application Software, Hardware, and Networking etc. for integration of 

any intervention with application during Operation and Maintenance Phase. 

As a part of Post-Implementation services, the Implementation Agency shall undertake the 

following: 

I. Annual Technical Support for Five years 

a. For Application Software 

b. For Server Hardware Supplied under this project 

c. For Client side Hardware supplied under this project 

At the end of each quarter during O & M phase: 

I. Updated system design documents, specifications, 

II. Latest source code, application deployment files, configuration files for entire 

solution 

III. Updated user manuals, administration manuals, training manuals etc. 

8.1 Warranty/AMC Applicability 

As part of the technical support requirements, the IA is required to provide support for 

Hardware, Software, and for components as further specified below. The support may be 

required selectively as described below. 

The applicability of Warranty/AMC for each of the components is as under: 

Component Warranty/AMC Applicability 

ASI Monument site - Client 

Side Hardware 

Applicable 

LAN including network Applicable 

switches 

Software Applications Applicable 



Warranty 

AMC 

Server – Hardware Applicable 

IA shall provide a comprehensive warranty and on-site free service for all the new 

hardware procured as part of this RFP 

IA shall obtain the Five year product warranty and Five year onsite free service warranty 

on all application software, Server hardware and other equipment from the OEMs. 

The IA is responsible for sizing and procuring the necessary hardware as per the 

performance requirements provided in the RFP. During the warranty period the IA shall 

replace or augment or procure higher configuration equipment at no additional cost to 

ASI in case the procured hardware is not adequate to meet the service levels. 

IA shall provide comprehensive manufacturer's warranty in respect of proper design, 

quality and workmanship of all hardware, equipment, accessories, etc. covered in the 

RFP. The IA must warrant all hardware, equipment, accessories, etc. procured and 

implemented as per this RFP against any manufacturing defects during the warranty 

period. 

The IA shall monitor warranties to check adherence to preventive and repair 

maintenance terms and conditions. 

The IA shall provide the performance warranty in respect of performance of the installed 

hardware and software to meet the performance requirements and service levels in the 

RFP. 

During the warranty/AMC period IA shall maintain the systems and repair / replace 

at the installed site, at no charge to ASI, all defective components that are brought 

to the IA's notice 

The IA shall monitor OEM warranties to check adherence to preventive and repair 

maintenance terms and conditions. 

The IA shall ensure repair and replacement of hardware after the problem has occurred. 

The IA shall as far as possible repair the equipment 

Software Applications 

Warranty and AMC of the Application Software 



The IA shall provide logging mechanism to report software problems /defects. The IA 

shall facilitate ASI easy access to the issue log, status of the problem/defect, and the 

description of the resolution. 

The IA shall maintain record of entitlement and provide software upgrade/maintenance 

patches for application software including OEM software. 

The IA shall carry out any requisite amendments/ changes in the configuration for 

implementing such patches. The IA shall ensure that any new patches do not degrade the 

application performance and shall comply with the SLAs. 

Technical Support Services 

Technical Support services shall be provided for a period of 5 years from the date of Final Go 

Live during normal working hours of ASI offices. These services shall be accessed through a 

Single Point of Contact (SPOC). The IA is expected to plan for contingencies. 

I. Provide Technical Support for reporting Monument site user incidents / issues / problems 

and also Online users 

II. Provide necessary channels for reporting issues round the clock. The incident reporting 

channels could be the following: 

i. Specific E-Mail account 

ii. Online reporting through a web based form 

III. Implement a call logging system in line with the severity levels as per the SLAs. The SPOC 

shall log user calls related to ASI and assign an incident/ call ID number. 

IV. Escalate the calls, to the appropriate levels, if necessary as per the escalation matrix 

agreed between the IA and ASI. The escalation matrix shall be developed by the IA in 

discussion with ASI 

V. Coordinate with respective OEM for closure of calls. 

VI. Creation of knowledge base on frequently asked questions to assist user departments in 

resolving basic issues themselves. 

VII. Provide feedback to callers. 

The IA to provide support services to track and route requests for service and to assist end 

users in answering questions and resolving problems related to software applications, at 

monument sites. 

8.2 SLA Management Tools 

I. SLA management tool should be able to monitor the all the service levels defined in the 

service level agreement. 

II. The proposed SLA management tools should automatically document problems and 

interruptions for ETS services and provide the consolidated violations as per the SLA 

III. The Tool should allow configuring the parameters of the measurement and should allow 

adding new SLAs on need basis. 



IV. SLA management tool should enable the ASI to have a unified view of the entire ETS 

system SLA at single console. 

V. The proposed solution should provide the following performance reports. 

a. Executive Summary report that gives an overall view of a group of elements, 

showing volume and other important metrics for the technology being viewed. 

b. Capacity Planning report which provides a view of under-and-over-utilized 

elements. 

c. Service Level report that shows the elements with the worst availability and 

worst response time-the two leading metrics used to monitor SLAs. 

d. The proposed system must have a built-in report authoring tool which will enable 

complete customization flexibility of performance reports. 

e. The tool should provide an integrated performance view for all the managed 

systems and networks along with the various threshold violations alarms in 

them. It should be possible to drill-down into the performance view to execute 

context specific reports. 

VI. The proposed tool should be able to monitor various operating system parameters such 

as processors, memory, files, processes, file systems, etc. where applicable, using agents 

on the servers to be monitored. 

VII. The proposed solution should provide self-monitoring wherein it will track critical status 

such as 

a. CPU utilization 

b. Memory capacity 

c. File system space and other important data. 

Other Operational Requirements 

Services required at the Monument site - Point of Sale 

At the monument site the Point of Sale (POS) essentially acts as the front post for all 

ticketed related services. These counters are meant for all visitors whether they have 

requisite access to IT infrastructure/ skills to transact online with internet ticketing portal or 

not. The online route shall offer distinct advantages to the visitors as they shall not have to 

stand in long queues at the ticket counters and can easily secure access through a channel 

at the monument during the time of visit. The scope of work for POS is broadly categorized 

into Information Services and Transaction Services in the following sections. 

1. Information/Transaction Services 

In addition to the regular counters that shall issue tickets to Indian and foreigner visitors, 

minimum of one POS counter shall also be provided for Information Services to the visitors 

to help/ guide them 

2. Productivity of POS staff 



The IA will provide manpower for all staff at the ticket counters and at the checking 

counters. The efficiency and image of ticketing system will depend largely on the efficiency 

and customer-friendliness of the operators/ officers who man the counters at the POS. It is 

in the interest of ticketing system, and therefore of all the stakeholders that every effort is 

made to enhance the efficiency and customer-orientation of POS staff to optimum levels. 

The following guidelines are provided in this regard: 

- The IA shall exercise due care and caution while selecting the operators with the 

right skill sets including the proficiency in English, Hindi and local language of the 

respective state where a Monument is situated 

- The IA shall impart necessary pre-job training and orientation to the operators on 

the ticketing system so that they are all at acceptable levels of efficiency to begin 

with. 

- The IA shall provide ticketing staff with necessary behavioral training in order to 

imbibe customer and service orientation in them 

- The IA shall also impart necessary in-service training, for duration of at least two 

days to all the operators, once in a period of 6 months. 

- ASI may prescribe suitable norms on efficiency of the counter-operators. In case a 

counter operator fails to achieve the efficiency norms consistently, ASI may advise 

the IA to take suitable steps to replace such an operator. 

- IA shall ensure that staff replaced in a year does never exceed 10% of the total POS 

staff deployed by him 

- There will be enough contingencies planned to ensure smooth operations 

- The ticketing staff to ensure before closing to run the script for the local database 

sync with the central database 

- All devices used for the ticketing functions will be safely stored under lock and key 

and an inventory ( Including spares) of the same will be maintained at the site 

- The IA shall deploy an operations manager at World Heritage monuments and 

category A. Monuments. 

3. Fee Collection and related processes 

- All staff has to be trained on handling currency counting machines available at 

Category A ( high footfall) monuments 

- All staff has to be trained on handling fake currency detector 

- The ticketing staff has to ensure that all cash collected shall be stored in a 

currency chest 

- The IA shall provision for IA to deposit all collections from ticket sale to an 

authorized bank account of that circle of ASI, to be remitted in the Government 

treasury latest by the next working day 

- IA will have to make necessary arrangements for handling the cash collected at 

POS and its transfer to ASI Bank Account 

- Insurance and security of cash will also be the responsibility of the IA. 



- IA ill itefae the tiketig sste ith A“Is Bak Offie “ste fo poidig 

an up-to-date account of the no. of tickets sold and revenue generated from 

ticket sale. 

- The staff will ensure an acknowledgement of the cash deposited with ASI 

Manpower Deployment Requirements 

1. The manpower shall be deployed by the IA for executing operations, management 

ad aiteae of the Tiketig sste ad fo all PO“s, as pe tes speified i 

this RFP and agreed with ASI 

2. The POS operators should be fluent in English, Hindi and local language of the 

respective state where a POS is situated and should have a certificate from any 

recognized computer institute showing that he/ she knows the basic operations of 

computer and office packages. 

3. All the personnel deployed by the IA shall furnish the proof of appointment by the IA 

at the time of joining the duty 

4. The attendance registers will be maintained by the IA at the respective monument 

locations 

5. IA shall be fully responsible for any loss or mishandling of cash and other 

documents/assets by any of its personnel ad eleat “LAs shall e iposed. 

6. The IA will maintain adequate leave reserve for personnel deployed. 

7. The personnel deployed by IA should be employees of the IA and they will have 

absolutely no claim to any category of appointment in any Government organization. 

8. The terms of employment for the personnel deployed by the IA shall be strictly as 

agreed between them and the IA. Also, IA shall be completely responsible for 

payment of salary, perks, incentives, any monetary & non-monetary compensation 

and all statutory contributions like Insurance, ESI & PPF etc.to the personnel 

deployed. 

9. The personnel attending to duty shall display a proper identification badge as 

prescribed by ASI 

10. A toutig atiit take up IAs pesoel ill e take e stogl agaist IA 

and necessary action will be taken by ASI against the personnel and/or IA 

ASI reserves its right to subject all personnel/ subcontractors deployed by IA on Ticketing 

Project related work to security clearance before IA issues appointment letters to them. For 

this IA will have to provide ASI the complete list of all such personnel/ subcontractors 

atleast 60 days in advance before they start their work 

Monument Ticket: 



The design of ticket should be such that the visitors obtain services with speed and 

certainty. An indicative specification of the proposed ticket is mentioned below. However 

the IA is expected to a detailed study during the SRS stage. 

Ticket Size: 50mm x 102mm 

Ticket Type: Direct Thermal 

Color: Multi color (front side), Single color (back side) 

Thickness: 150 to 200 GSM 

The tickets shall be printed at the Point of Sale sites only and the process of centralized 

ticket printing at India Security Press Nashik shall be done away with. The switchover to the 

POS ticket printing, which is a real time printing, shall take place gradually for monuments 

across all categories. 

The details including monument picture, about the monument, date, barcode etc. needs to 

be printed on each ticket which shall be finalized in consultation with ASI. Though the tickets 

printed will be bi-lingual, the visitor will have to enter the required information for ticket 

booking on portal in English ONLY. The same shall hold true for the ticket operators 

manning the POS system. 

Online Sales Channel 

Internet ticketing: The IA will design and host the web portal for sale of tickets that shall 

support secure payment gateway for payments through Credit Cards, Debit Card and Net 

Banking. The online order shall use HTTP SSL and XML technologies for secured transactions. 

Internet ticketing solution shall be integrated with Point of Sale solution. 

Multiple delivery Channels 

Print at home/Print in Advance – Visitors shall have the option to print tickets some time 

before the actual visit or at the day of visit from the Point of Sale site. 

The tickets booked online shall be emailed / SMSed to the isitos otat i a o-editable 

format. 

Back-office Channel 

The Point of Sale terminals shall Print On Time/ Real time selling, printing each ticket at the 

ticket window that is connected to a centralised database. In case there is no connectivity 

the POS solution shall work as a standalone module and shall in no way effect the 

operations and ticket printing. On resumption of connectivity the transactional data shall be 

uploaded to the centralised database in a batch mode at a predefined frequency. 

Entry Ticket Validation (ETV) 



The entry ticket validation shall be performed with the help of hand-held bar code scanners. 

These handheld scanners deployed at the entry gates shall essentially be of wireless type. 

These have to be sufficiently charged before being put into operations. IA shall have to 

maintain enough spares at each site. IA has to ensure that there shall be no interference in 

the line of sight between the handheld scanners and their base charging units. The handheld 

bar code scanners shall either be connected to the centralised system or to a local 

system at monument site that shall be further web-enabled to synch that data with the 

centralised system. 

The volumes of transactions have been given for last three years in Annexure. ASI does not 

guarantee any particular volume and bidders will be required to make their own assessment 

on the basis of past data and other socio-economic indicators 

All functionality expected to be performed by the visitors through the ETS portal should 

require the use of only free and freely available software 



9. Requirements of Project Implementation 

The overall implementation of the e- Ticketing system is envisaged to be completed in 12 

months. 

Implementation Model: The entire implementation would consist of a system based on 

application customization and Configuration to the needs of ASI. The Implementation is 

expected to be completed within 12 months from the date of selection of the IA. 

The following responsibility matrix depicts the broad aspects of the implementation model: 

Sl. No. Aspect Responsibility(R)/Ownership(O) 

IA ASI 

1. Implementation, deployment and 

operation of the project 

Yes (R) - 

2. Testing of application modules Yes (R) 

3. Procurement and setup of the 

server side infrastructure 

4. Procurement of client end 

hardware, software and LAN 

5. Procurement of Data Centre and 

DRC services and facilities 

6. Ownership of all IT infrastructure, 

application, system software and 

all related components 

7. Audit & Certification of the 

application prior to go-live 

Yes (R) (O) 

Yes (R) (O) 

Yes (R) (O) 

Assist and enable 

ASI (R) - 

8. Program Governance Yes (through the 

Program 

Manager) 

Table 4: Responsibility Matrix 

Server Side 

Client Side 

(O) 

Yes (through a 

third party 

audit agency) 

(O) 

Yes (through a 

POC & PMU) 

(All Hardware and Software procured by the IA under this project will be owned by ASI) 

9.1 Approach & Methodology for Implementation of Technical Solution Project 

Implementation Model 

The e-Ticketing project shall be designed, built and operated on an outsourced model 

wherein the pojets desig, ustoizatio, tiketig opeatios ad opeatio & 

maintenance shall be outsourced to a private agency to be known as Implementation 

Agency and selected through a competitive bidding process subject of this RFP. This 

model is adopted to facilitate utilization of private resources and expertise for 

implementation and operation & aiteae ad at the sae tie to etai A“Is 

control over the system design (through conformance to RFP requirements), 



Customization/Configuration (through conformance to standards) and operation & 

maintenance (through conformance to SLA). 

The implementation of the application would be phased in progressively, covering 

successively different geographies and Monuments. A summary of the Approach for 

Implementation is provided below for better understanding of the Bidder. 

Progressive Rollout Approach with Timelines 

Sr. No Phases Locations Modules Timelines 

1 Round – 1 10 ( World 

Heritage 

Monuments & 

Category A 

Monuments ) 

( As specified in 

the Annexure) 

2 Round – 2 For the Next 10 ( 

World Heritage 

Monuments & 

Category A 

)Monuments 

3 Round – 3 25 Monuments ( 

As specified in 

Annexures) 

Centralized 

application for POS 

& Online ticket 

issuance along with 

Handheld device 

Application 

Centralized 





Application 

Centralized 





Application 

T + 14 weeks 

T +26 weeks 

T + 36 weeks 






Annexures) 

5 Round -5 41 Monuments ( 


Annexures) 

Table 5 : Timelines and Deliverables of the Project 

9.2 Detailed Project Implementation Schedule 

Centralized 





Application 

Handheld Device 

application 

T + 46 weeks 

T + 52 weeks 

S. N. Milestone Time for 

Completion (in 

weeks) 

1. Study, preparation of FRS & SRS and Design Documents and 

Solution Customization/Configuration 

2. 

Site preparation for core infrastructure at DC, DRC 

3. Deployment of Central hardware and application at DC and DR 

after third party audit of the application (POS , Online & 

Handheld Module) 

4. Site Preparation, Installation of IT components, Hardware, 

Software, Internet Connectivity , Networks etc.- Round 1 

Monuments 

5. Configuration of Application (POS , Online & Handheld Module) 

with commissioned Infrastructure on site & Testing – Round 1 

Monuments 


T+6 

T+8 

T+9 

T+10 

T+12


6. Implementation of Application(POS , Online & Handheld) at the 

for first 10 World Heritage Monuments & Category A 

monuments – Round 1 Go Live 

7. 

Site Preparation, Installation of IT components, Hardware, 


Monuments 

8. Implementation of Application (POS & Online Module) for next 

10 World Heritage Monuments & Category A Monuments – 

Round 2 


Software, Internet Connectivity , Networks etc. for site- Round 3 

locations 


POS for 25 monuments – Round 3 Go Live 



locations 



T+14 

T+24 

T+26 

T+26 

T+36 

T+ 36 

T+ 46 

13. e- Ticketing documentation and Project documentation T+46 


Software, Internet Connectivity , Networks etc. for site -Round 5 

locations 



16. Overall e-Ticketing System Operation and Maintenance 

Support 

Table 6: Implementation Schedule 

*T - indicates the project kick-off date 

T+ 46 

T+52 

T+52 to 312 

Bidders are advised to study the implementation approach carefully and propose the 

technical solution based on the implementation approach. It is expected that fo go-lie 

of each round, Bidder would provide, application hosting, client infrastructure, server 

infrastructure and provide trained personnel. 



The Final Go live will be considered from 90% of successful transactions from e-Ticketing 

Solution for World heritage, Category A & B type Monuments. 

Final Go Live will be based on following Criteria: 

Successful Implementation of Online Solution, POS Solution & Handheld Solution for 

atleast 3 months from T+ , eetig all the pesied “LAs etioed i ‘FP 

100% Reconciliation of tickets sold and cash received through all the channels 

(Online and POS) 

Closure of all the errors and bugs (Show Stopper Category) reported within 3 months 

from T+52. 

9.3 Project Management Plan 

Bidder is expected to follow the schedule as mentioned. Each of the milestones should be 

accompanied with a presentation on the deliverables by the bidder, related to that 

milestone. The submission of deliverable will be deemed complete after the submission of 

the hard / soft copy of the deliverable and the presentation by the bidder. 

The Epeted Date of Copletio as etioed i the tale above is the date by which 

the deliverable shall be submitted to ASI. The Bidder shall ensure that the deliverable is 

accepted by ASI as per schedule mentioned in the table above post review. 

The IA shall follow prudent project management practices commensurate with the best 

international standards during the course of the project implementation. While the actual 

process of software Customization/Configuration will remain an internal activity of the IA, it 

is important that ASI or their designated advisors shall have adequate visibility into such 

processes. 

The following are some of the major guidelines to be kept in mind for Project Management. 

1. Scope Management: The requirements in general and the customization requirement in 

particular, shall be collected and documented clearly. The scope and Requirements shall be 

controlled against a baseline and any changes shall be communicated to ASI and 

documented. 

2. Time Management: IA shall prepare a detailed project schedule conforming to the stakeholder 

expectations and exercise stringent control of the schedule. A periodic report on the 

progress and deviations should be shared with ASI. Any schedule conflicts with respect to 

project and/or deliverable timelines will have to be resolved by IA in consultation with ASI 

and/or its designated agencies and approved by ASI. Thereafter the approved timelines will 

have to be adhered to by IA, unless specified otherwise. 



3. Quality Assurance and Quality Control: A detailed Quality Assurance Plan shall be 

prepared and shared with ASI. The same shall be monitored and IA shall share a periodic 

report on the quality activities. These shall include: 

a. Architecture and Design Review Reports 

b. Test Plans Review Reports 

c. Test Execution Review Reports 

4. Project Risk management: IA shall document the risks during implementation and share 

the same with ASI. This shall be periodically reviewed and shared with ASI. A report on the 

periodic risk analysis, risk responses planned, mitigation strategies executed shall be shared 

with ASI. 

The IA shall store all the Project Management and Delivery artifacts into a secure 

configuration database and give access to ASI for view purposes. During the O&M period, 

any change requests and enhancements to the software shall be similarly documented so as 

to create a comprehensive repository of all artifacts relevant to ASI stakeholders. This will 

serve as a valuable knowledge input during Exit Management and also for any statutory 

audit. 

9.4 Project Deliverables 

The Implementation Agency has to deliver the following deliverables to ASI as part of 

assurances to fulfill the obligations under the SLA. The table given below may not be 

exhaustive and IA is responsible to provide all those deliverables which may be specified in 

this RFP but not listed here and those agreed by IA in response to any request from ASI. 

It is to be noted that upon completion of Go-live, IA is required to submit / handover all 

the updated system design documents, specifications, source code, application 

deployment files, user manuals, administration manuals and all other applicable 

deliverables listed below. IA shall handover source code of customized development 

irrespective of open source or proprietary software. 

S.N. Deliverables 

1. 3Inception 

Report 

. 

2. 4Detailed 

project plan for study, design, Customization/Configuration & 

. implementation of e-Ticketing system covering the various components on 

Infrastructure, Manpower etc. The plan should clearly identify all the 

milestones and deliverables together with the tasks and time & resource 



allocation. 

3. 5Functional 

Requirement Specification Document (FRS) and System Requirement 

. Specifications (SRS) Document 

4. 6a. 

Technical / System Design Document (HLD and LLD) including but not 

. limited to 

Logical and Physical Data base Design 

Logical Data Dictionary and data / file formats 

Application architecture, deployment architecture, network architecture 

diagrams, security architecture etc. 

Component, and Deployment Views of the Application 

Collaboration, Class diagrams in the UML notations 

Security and Features 

Performance Features 

Interface / Control Design Features 

b. Traceability Matrix 

c. Document on Testing Approach for e-Ticketing Application, along with the 

test cases and test results including but not limited to 

Type of Inputs ( functional / performance / stress / Acceptance / 

structural) also including Test Coverage / boundary conditions 

Machine Configuration 

Test Assumptions 

Test data as applicable 

Response Time / Execution Time / Throughput 

5. 7a. 

Developed and customized e-Ticketing solution 

. 

6. 8 

. 

Reports on Various Tests performed for e-Ticketing Solution along with the 

results & plan for addressing the issues identified during Testing 

7. 9a. 

IT Infrastructure solution encompassing Network, Servers, Database, System 

. Software, including deployment and collocation at Data Center and Disaster 

Recovery Center 

8. 1Establishing 

the IT & non-IT infrastructure at the ASI Project locations/ 

0Monument 

sites 



. 

9. 1a. 

Security policy 

1b. 

Standard Operating Procedures 

. 

10. 1a. 

Defect Free e-Ticketing Application Software and other automation 

3 requirements including Source Code, library files, DLLs, Setup programs, 

. Documentation, etc. 

b. Updated & Final System Requirements and Design Documents 

11. 1 

c. Maintenance Manuals for Administration and Maintenance of e- Ticketing 

system 

d. SLA Monitoring & Measurement system using EMS and other tools / 

applications 

e. Technical helpdesk and support 

4 

. 

Project Documentation 

12. 1a. 

Post Implementation Support to ASI 

5b. 

Daily/Weekly/for-nightly/monthly Performance Monitoring Reports for the 

. e-Ticketing System 

13. 1At 

the end of each quarter, during O & M phase: 

6a. 

Updated system design documents, specifications, 

. b. Most recent source code, application deployment files, configuration files 

for entire solution 

c. Updated user manuals, administration manuals, etc. 

d. Software change logs etc. 

Table 7: Project Deliverables 


RFP for e-Ticketing Project Volume-I 

10. Governance 

Putting a governance structure aoud A“Is futue IT ipleetatio pla is essetial to 

ensure that project implementation stays on track and achieves its strategies and goals. It 

acts as a mechanism to measure the progress of the implementation. Also, IT systems today 

are subject to many regulations such as governing data retention, confidential information, 

financial accountability and recovery from disasters. An IT governance framework is an 

efficient system to ensure regulatory compliance. 

Overall responsibility for the implementation of the e ticketing system will remain with the 

IA. Project progress review and monitoring will be the responsibility of PMU during project 

implementation phase. ASI will appoint a Single Point of Contact (SPOC) for IT 

Administration. Escalation of all issues related to the system will be through this SPOC, who 

will also be responsible for reviewing the SLAs being met. For the project implementation 

phase, supervision and reporting during implementation will be responsibility of PMU. 

10.1 Key stakeholders of the project 

A three-tier IT Governance structure may be constituted considering the wide scope of 

project at ASI. This three-tier structure can be divided into the following groups: 

i. Project Steering Committee (SC) 

ii. Project Operations Committee (OC) 

iii. Project Management Unit (PMU) 

10.2 Project Steering Committee 

ASI shall have the overall responsibility for policy directives, guidance and coordination for 

activities related to e-Ticketing project. At a strategic level, this responsibility is vested with 

the Steering Committee (SC). The SC is chaired by the DG, ASI. The SC plays a key role in 

guiding and advising on the project implementation and the systemic transformation that 

the project aims at. The SC shall monitor project implementation at the national level by 

coordinating with the Project Operations Committee (POC) and the Project Management 

Unit (PMU). 

The IA to get support from the SC on the following guidelines: 

i. Guiding the work of Operations Committee 

ii. Periodic Review of implementation progress 

iii. Consider recommendations put forward by the Operations Committee 

iv. Strategic control over the project


10.3 Project Operations Committee 

Project Operations committee under the guidance of SC is responsible for successfully 

managing the implementation of the project. Operations Committee is headed by the ADG, 

ASI. 

The IA will be working with the POC on these points: - 

i. Overseeing and directly supervising the project implementation 

ii. Seeking directions and guidance for the project implementation 

iii. Vetting of all deliverables of the project and recommend the same for 

acceptance by the steering committee 

iv. Coordinating with the relevant officers at all levels for effective implementation 

of the project and helping resolve issues requiring high level interventions 

v. Carrying out related tasks as may be reasonably requested by the SC 

vi. Address concerns / enquiries / complaints referred to the OC by ASI employees 

vii. Developing and overseeing procedures for undertaking quality audits of 

institutions participating in the project 

viii. Assist in execution of the vision for change management 

ix. Ensuring effective transfer of knowledge and lessons learnt to the people 

involved within and across ASI project locations 

x. Resolve any conflicts and issues that may arise during the implementation of the 

project. 

10.4 Project Management Unit (PMU) 

PMU would consist of consultants with experience in information technology and quality 

control. Project Manager of the PMU shall report to the Project Operations Committee. The 

PMU shall have specialists in the areas pertaining to software application, change 

management and infrastructure management and shall be responsible for day to day 

management and coordination, and operational activities. 

The PMU will provide information and examples of good practice, and guide and support 

the various entities involved on all aspects of project implementation. It also includes, 

wherever required, efforts to build capacity of ASI. The PMU shall be headed by a Project 

Manager. 

The PMU has overall responsibility for the management of the project and is accountable to 

POC. The responsibilities of the PMU are: 

i. Overseeing and assisting the project implementation 

ii. Providing directions and guidance to implementation agency for project 

implementation 

iii. Coordinating with the relevant officers at all levels 



iv. Carrying out related tasks as may be reasonably requested by the OC 

v. Help in laying down a set of guidelines, following internationally accepted norms and 

e-Governance standards, if not present already, for the testing and certification in all 

aspects of project development and implementation covering software, hardware 

and networking. This includes the processes relating to the design of systems and 

sub-systems, coding, testing, business process 

vi. Ensure that all relevant guidelines are being followed and to avoid large-scale 

modifications pursuant to testing done after the application is fully developed 

vii. Establish appropriate processes for notifying the implementation agency of any 

deviations from the norms, standards or guidelines at the earliest instance after 

noticing the same to enable them to take corrective action 

viii. Ensuring full knowledge and systematic application guidance to the implementation 

agency in the initial stages and the testing and approval of the deliverables at the 

intermediate stage and finally the monitoring and analysis of reports 

ix. Monitoring the internal operations of the project utilization 



11. Change Management 

This section focuses on the change management and capacity building approach and plan so 

as to be able to tackle the issues that might arise due to new processes and use of e- 

Ticketing at monuments. Training for e-Ticketing Project will allow multiple stakeholders to 

participate in the day to day ticketing operations at the monuments. 

Need for Change Management 

Introducing radical reforms has to be necessarily accompanied by efforts to energize and 

orient the mindsets of the people – both within and outside the department. For instance, 

the ASI staff should be skilled to operate and work in a significantly newer and different 

way. It is necessary to formulate a change management plan with appropriate interventions 

for capacity building, training and stakeholder communications. 

A successful Change Management Program will ensure: 

A smooth transition to the new way of working and ticketing at monuments 

Communication strategy for visitors as part of the plan 

Individual stakeholders understand how the changes affect them and the role they 

have to play 

Stakeholders to understand the benefits of the changes and internalize it 

The new system and its underlying concepts are understood 

People are aware of how roles, responsibilities and processes are changing 

Change Management Plan 

It will be critical to assess those issues that will have the highest impact on the change 

management plan and manage them through appropriate interventions. Some of the 

interventions proposed are listed below: 

Create awareness for both Indian and Foreign visitors of the new system 

Create awareness among all key stakeholders on the benefit of the new system 

Help to make staff realize the benefits of the new system 

Identification and preparation of change agents (change champions) to deal with 

change at local level i.e Monuments 

Highlight the ease of working in the new system with better technology and simpler 

processes 

Key steps for Change Implementation 

Intervention at various levels is needed to mitigate staff resistance to change and facilitate 

an environment which encourages staff to pro-actively volunteer within the new system. 

Some of the strategies to ensure quick-wins would be: 



The proposed changes highlighting the benefits of the system and thus winning the 

confidence of ASI staff 

Provide with answers to key questions which users will encounter 

Communicate with visitors the key requirements of the proposed system- What e 

at fo the. Thee eatig fous fo dialogue ad ehage of ideas 

Use communication mechanisms for providing the ASI staff with critical information, 

feedback mechanisms and support during the change of system 

Skill enhancement through training of the staff (functionality and technology) 

ASI staff deployed at monuments may resist significant changes due to fears of 

retrenchment. Officers should acknowledge these feelings and address them through faceto-face 

meetings and other communication strategies. 

Approach to Capacity Building 

It is important to build capacities of ASI and its staff in terms of necessary knowledge and 

skills to initiate and successfully implement the new system. Some of the real problems 

faced at the various levels are: 

Little knowledge on essentials of IT 

Minimum technology exposure 

Lack of in-depth understanding of the benefits 

To address the training needs, the change management team should prepare guidelines that 

identify the training needs of all stakeholders. Such guidelines will aid the progress of the 

implementation of the new system efficiently. 

Main Training Modules 

Based on their needs and the objectives of ASI e-Ticketing initiative the following program 

needs to be addressed:- 

a) Training to be imparted to Project steering committee, Project operations 

committee, Project implementation Unit selected by ASI, Site Incharge and other ASI 

staff deployed at monuments on Application, Behavorial and System training for SLA 

monitoring 

A detailed training roadmap will also have to be elaborated by IA for training and swift 

handover of operations to ASI or other contracted agency post expiry of O&M period. 



12. Documentation Requirements 

End-User Documents 

Documentation will be supplied and maintained by the Implementation Agency during the 

project. The ownership of all documents, supplied by the Implementation Agency, will be 

with ASI. The electronic copies shall be submitted along with all the paper documents and 

manuals, required for operating and configuring the system. The documents provided must 

include at least: 

User Manual (both online and paper copies) providing detailed instructions on how 

to use the software. In addition, it describes how to access, submit inputs to, and 

interpret outputs from the application 

System installation guide including the configuration of the supplied infrastructure. 

User will have the rights to duplicate the hardcopy and soft copy for the 

documents created by the Implementation Agency without any financial and legal 

implications 

e-Ticketing Application Training Manual 

Technical Documents: 

The Implementation Agency must ensure that the e-Ticketing system components being 

developed are thoroughly documented with comprehensive manuals and adhere to 

standard methodologies in software development as per ISO and/or CMM models. The 

documents including but not limited to are: 

Product installation and configuration steps; 

Application access procedures; 

User screen layout and content; 

Transaction entry procedures; 

Batch job setup, processing, and recovery/restart procedures; 

Error codes with full descriptions and recovery steps; 

Standard report layout and content; 

Internal processing controls; 

Application security; 

Operating specifications and system flowcharts; 

Database entity relationships, table formats, and data element 

descriptions; and Program module descriptions 

Quality Assurance Plan Documenting the planned and systematic pattern 

of all actions necessary to assure confidence that the software developed 

will conform to the ASI functional and technical requirements. 



Interface Control Document Documenting the interface characteristics of 

one or more systems and documents agreements between interface 

owners. It contains information on both the physical and data element 

requirements that are necessary to make the transfer of information 

between systems feasible. 

Test Plan Containing information on the software test environment to be 

used for independent testing, the test cases to be performed, and the 

overall testing schedule. This includes methodology, schedule, resources, 

tools, procedures, environment definition, test cases, and software test 

results. 

Systems Manual Detailing the data structure, table, forms and report 

structures. 

Installation and maintenance manual for the servers and other hardware 

Operations Manual providing instructions for installing the application, 

troubleshooting, interpreting message logs, and FAQs (Frequently Asked 

Questions). 

Trouble Shooting Guide/ Handbook which describes the various trouble 

shooting methods. 



List of Monuments 

Round 1 Implementation 

S.No Name of Monument 

Total 

Footfall 

Category Counters 

ANNEXURES 

Manpower 

Required 

PC Printer Scanner 

Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Operation 

Manager 

Total 

Manpower 

1 Taj Mahal 54,77,381 WH 12 12 6 3 10 10 4 4 1 54 

2 Agra fort. 19,71,034 WH 4 4 3 3 4 4 2 2 1 22 

3 Fatehpur Sikri 6,80,196 WH 3 3 2 2 4 2 1 1 1 14 

4 Ajanta Caves 4,40,325 WH 2 2 2 2 2 2 0 0 1 10 

5 Ellora Caves 13,64,460 WH 4 4 3 3 4 4 2 2 1 22 

6 

World Heritage Site, 

Hampi 4,89,905 WH 2 2 2 2 2 2 0 0 1 10 

7 

Western Group of 

Temple, Khajuraho 3,43,333 WH 2 2 2 2 2 2 0 0 1 10 

8 

Buddhist monuments, 

Sanchi 2,13,456 WH 2 2 2 2 2 2 0 0 1 10 

9 Sun Temple Konark 22,39,820 WH 4 4 3 3 4 4 2 2 1 22 

10 

Group of Monument, 

Mamallapuram/Mahaba 

lipuram 10,86,041 WH 4 4 3 3 4 4 2 2 1 22 

Total 39 39 28 25 38 36 13 13 10 196




Total 

Footfall 

Category Counters Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Operation 

Manager 

Total 

Manpower 

Group of Monuments (WH), 

Pattadakal 3,40,262 WH 2 2 2 2 2 2 0 0 1 10 

1 

2 Red fort 28,54,149 WH 4 4 3 3 4 4 2 2 1 22 

3 Humayun's Tomb 7,92,402 WH 3 3 2 2 4 2 1 1 1 14 

4 Qutb Minar 33,97,609 WH 4 4 3 3 4 4 2 2 1 22 

5 Elephanta Caves 

Jami Masjid, Champaner- 

3,96,128 WH 2 2 2 2 2 2 0 0 1 10 

6 Pavagadh Saher ki Masjid 

Champaner Pavagadh 1,17,929 WH 2 2 2 2 2 2 0 0 1 10 

7 Bibi ka Maqbara 12,50,521 A 4 4 3 3 4 4 2 2 1 22 

8 Gol-Gumbaz, Bijapur 10,82,359 A 4 4 3 3 4 4 2 2 1 22 

9 Charminar 14,68,937 A 4 4 3 3 4 4 2 2 1 22 

10 Golconda 14,97,219 A 4 4 3 3 4 4 2 2 1 22 

` 

Total 

33 

33 

26 

26 

34 

32 

13 

13 

10 176




Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpower 

1 

Akas To, 

Sikandara 5,33,433 B 3 3 2 2 4 2 1 1 12 

2 Daulatabad Fort 

Daria Daulat 

Bagh, 

6,44,709 B 3 3 2 2 4 2 1 1 12 

3 Sriragapatna 9,60,315 B 3 3 2 2 4 2 1 1 12 

4 Jantar Mantar 5,05,060 B 3 3 2 2 4 2 1 1 12 

5 Purana Qila 7,78,549 B 3 3 2 2 4 2 1 1 12 

6 Chittaurgah Fort 5,14,531 B 3 3 2 2 4 2 1 1 12 

7 Hazarduari Palace 6,96,745 B 3 3 2 2 4 2 1 1 12 

8 Shaniwarwada 

Excavated 

Remains at 

7,50,748 B 3 3 2 2 4 2 1 1 12 

9 Nalanda 5,39,249 B 3 3 2 2 4 2 1 1 12 

10 Itimad-ud-Daulah 1,94,733 C 2 2 2 2 2 2 0 0 8 

11 Mehtab Bagh 1,12,671 C 2 2 2 2 2 2 0 0 8 

12 Pandulena Caves 1,86,166 C 2 2 2 2 2 2 0 0 8 

13 

14 

15 

Keshva Temple 

Somanathpur 2,31,257 C 2 2 2 2 2 2 0 0 8 

Tippu Palace 

Bangalore 1,68,055 C 2 2 2 2 2 2 0 0 8 

Chitradurga Fort 

Chitradurga 3,54,878 C 2 2 2 2 2 2 0 0 8



16 

Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpower 

Hoshangs Tomb, 

Mandu 1,66,964 C 2 2 2 2 2 2 0 0 8 

17 

Royal Palaces, 

Mandu 2,64,696 C 2 2 2 2 2 2 0 0 8 

18 Roopmati Pavilion 2,85,318 C 2 2 2 2 2 2 0 0 8 

19 Gwalior Fort. 2,70,734 C 2 2 2 2 2 2 0 0 8 

20 

21 

22 

23 

24 

25 

Udayagiri & 

Khandagiri Sites 

Gingee Fort, 

4,46,620 C 2 2 2 2 2 2 0 0 8 

Gingee 1,57,773 C 2 2 2 2 2 2 0 0 8 

Sheikh Chilli's 

Tomb Thanesar 1,08,818 C 2 2 2 2 2 2 0 0 8 

Durga Temple 

Complex, Aihole 2,38,458 C 2 2 2 2 2 2 0 0 8 

Jaina & Vaishnava 

Caves, Badami 4,51,375 C 2 2 2 2 2 2 0 0 8 

Ibrahim Rouza, 

Bijapur 2,42,998 C 2 2 2 2 2 2 0 0 8 

Total 59 59 50 50 68 50 9 9 236




Total 

Footfall 


Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpower 

1 

Karenghar of Ahom 

Kings, Sibsagar 1,68,285 C 2 2 2 2 2 2 0 0 8 

2 Amaravathi 17,990 C 2 2 2 2 2 2 0 0 8 

3 Nagarjunakonda 1,32,477 C 2 2 2 2 2 2 0 0 8 

4 Warangal 1,11,727 C 2 2 2 2 2 2 0 0 8 

5 Chandragiri 1,03,018 C 2 2 2 2 2 2 0 0 8 

6 

Kambhalgarh Fort 

Distt.Rajmand 1,92,850 C 2 2 2 2 2 2 0 0 8 

7 Koch Bihar Palace 4,01,254 C 2 2 2 2 2 2 0 0 8 

8 Sahet Sravasti 1,57,938 C 2 2 2 2 2 2 0 0 8 

9 Jhansi Fort, Jhansi 2,99,762 C 2 2 2 2 2 2 0 0 8 

10 Residency, Lucknow 2,85,129 C 2 2 2 2 2 2 0 0 8 

11 Kanheri Caves 1,90,967 C 2 2 2 2 2 2 0 0 8 

12 Agakhan Palace 1,13,058 C 2 2 2 2 2 2 0 0 8 

13 Lenyadri Caves 3,68,093 C 2 2 2 2 2 2 0 0 8 

14 Karla Caves 2,12,935 C 2 2 2 2 2 2 0 0 8 

15 Raigad Fort 1,76,174 C 2 2 2 2 2 2 0 0 8 

16 

17 

18 

Ancient Site of 

Vaishali, Kolhua 1,47,630 C 2 2 2 2 2 2 0 0 8 

Sher “hah “uis 

Tomb, 

Sasaram/Sararam 2,15,979 C 2 2 2 2 2 2 0 0 8 

Old fort (Shahi fort), 

Jaunpur 1,76,961 C 2 2 2 2 2 2 0 0 8



19 

20 

21 

Total 

Footfall 


Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpower 

Excavated Remains 

at Sarnath 3,89,252 C 2 2 2 2 2 2 0 0 8 

Bekal Fort, Pallikkare, 

Distt. Kasargod 3,10,946 C 2 2 2 2 2 2 0 0 8 

Mattancherry Palace 

Museum, Kochi, 

Distt. Ernakulam 3,54,093 C 2 2 2 2 2 2 0 0 8 

22 

Sun Temple, 

Modhera 3,12,584 C 2 2 2 2 2 2 0 0 8 

23 Rani-ki-Vav, Patan 2,76,109 C 2 2 2 2 2 2 0 0 8 

24 

Maias To, 

Sikandara 31,520 D 0 0 0 0 0 0 2 2 4 

25 Ram Bagh 59,146 D 0 0 0 0 0 0 2 2 4 

26 Aurangabad Caves 50,116 D 0 0 0 0 0 0 2 2 4 

27 Bellary Fort, Bellary 5,565 D 0 0 0 0 0 0 2 2 4 

28 Buddhist Caves 15,830 D 0 0 0 0 0 0 2 2 4 

29 

30 

The Palace Situated, 

Burhanpur 52,772 D 0 0 0 0 0 0 2 2 4 

Bhojshala and Kamal 

Maulas osue 11,423 D 0 0 0 0 0 0 2 2 4 

Total 46 46 46 46 46 46 14 14 212




Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpowe 

r 

1 Rajarani Temple 

Ratnagiri 

31,004 D 0 0 0 0 0 0 2 2 4 

2 Monument 23,566 D 0 0 0 0 0 0 2 2 4 

3 Lalitagiri Monument 17,374 D 0 0 0 0 0 0 2 2 4 

4 

5 

6 

7 

8 

9 

Front Museum, 

Thirumayam 67,013 D 0 0 0 0 0 0 2 2 4 

Fort on Rock, 

Dindigul 28,030 D 0 0 0 0 0 0 2 2 4 

Moovarkoil 

Kodambalur 6,993 D 0 0 0 0 0 0 2 2 4 

Rock Cut Jain 

Temple, Sittanasal 33,161 D 0 0 0 0 0 0 2 2 4 

Natural Caven with 

Insription 

Eladipattam, 

Sittannavasal 33,521 D 0 0 0 0 0 0 2 2 4 

Suraj Kund, 

Faridabad 35,286 D 0 0 0 0 0 0 2 2 4 

10 

Temple and 

Sculpture Shed, 

Lakkundi 14,155 D 0 0 0 0 0 0 2 2 4 

11 Khan-I-Khana 15,766 D 0 0 0 0 0 0 2 2 4



Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpowe 

r 

12 Sultanghari Tomb 330 D 0 0 0 0 0 0 2 2 4 

13 Tughluqabad 44,437 D 0 0 0 0 0 0 2 2 4 

14 Kotla Feroz Shah 71,899 D 0 0 0 0 0 0 2 2 4 

15 Safdarjung Tomb 85,739 D 0 0 0 0 0 0 2 2 4 

16 

Ahom ‘ajas Palae, 

Garhgaon, Distt. 

Sibsagar 49,168 D 0 0 0 0 0 0 2 2 4 

17 

Ranghar pavillion, 

Jaisagar. 63,107 D 0 0 0 0 0 0 2 2 4 

18 Bisnudol, Joysagar. 

Group of four 

Maidams 

Charaideo, Distt. 

13,466 D 0 0 0 0 0 0 2 2 4 

19 Sibsagar 37,412 D 0 0 0 0 0 0 2 2 4 

20 Undavalli 71,268 D 0 0 0 0 0 0 2 2 4 

21 Guntuplli 19,294 D 0 0 0 0 0 0 2 2 4 

22 

Deeg Palace Deeg 

Distt. Bharatpur 35,094 D 0 0 0 0 0 0 2 2 4 

23 

Bishnupur Gr. of 

Temples. 88,651 D 0 0 0 0 0 0 2 2 4 

24 Rani Mahal, Jhansi 20,659 D 0 0 0 0 0 0 2 2 4 

25 Bhaja Caves 47,451 D 0 0 0 0 0 0 2 2 4 

26 Kolaba Fort 55,370 D 0 0 0 0 0 0 2 2 4 

27 Sholapur Fort 14,759 D 0 0 0 0 0 0 2 2 4 

28 

Remains of 

Patliputra, 96,322 D 0 0 0 0 0 0 2 2 4



29 

30 

Kumrahar 

Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpowe 

r 

Ruins of 

Vikramshila, 

Antichak 55,082 D 0 0 0 0 0 0 2 2 4 

Lord Cornwallis 

Tomb, Ghazipur. 19,096 D 0 0 0 0 0 0 2 2 4 

31 

Observatory Man 

Singh (Man Mahal), 

Varanasi. 6,323 D 0 0 0 0 0 0 2 2 4 

32 Laxman Temple 58,082 D 0 0 0 0 0 0 2 2 4 

33 Kangra Fort, Kangra 85,827 D 0 0 0 0 0 0 2 2 4 

34 

35 

36 

37 

38 

Rock- Cut Temple, 

Masroor 22,461 D 0 0 0 0 0 0 2 2 4 

Palace Complex at 

Ramnagar, District 

Udhampur 3,436 D 0 0 0 0 0 0 2 2 4 

Group of Temples at 

Kiramchi, District 

Udhampur 2,969 D 0 0 0 0 0 0 2 2 4 

Avantiswamin 

Temple, Avantipur, 

District Pulwama 18,536 D 0 0 0 0 0 0 2 2 4 

Ashokan Rock 

Edicts, Junagadh 37,472 D 0 0 0 0 0 0 2 2 4



39 

40 

41 

Total 

Footfall 


Manpower 

Required 



Entry 

Verifiers 

Handheld 

Devices 

Mobile 

Verifiers 

Total 

Manpowe 

r 

Buddhist Caves, 

Junagadh 55,234 D 0 0 0 0 0 0 2 2 4 

Baba Pyara Caves, 

Junagadh & Khapra 

Khodiya Caves, 

Junagadh 602 D 0 0 0 0 0 0 2 2 4 

Ancient Palace at 

Leh, Ladakh NA D 0 0 0 0 0 0 2 2 4 

Total 0 0 0 0 0 0 82 82 164 

Monument Categorization 

WH – World Heritage Site 

A – Monument receiving more than 10,00,000 annual footfalls 

B – Monuments receiving between 5,00,000 – 10,00,000 annual footfalls 

C – Monuments receiving between 1,00,000 – 5,00,000 annual footfalls 

D – Monuments receiving less than 1,00,000 annual footfalls


Monument Guidelines 

In World Heritage and Category A Monuments, there will be an Operations Manager. 

In World Heritage and Category A & B Monuments, Mobile device for Ticket issuance will be used for crowd management. 

In Category WH & A Monuments, there will be 4 counters [1 - Information Kiosk/cloak attendant, 1 -Foreign, 2 –Indian] 

In Category B Monuments, there will be 3 counters [1 - Information Kiosk/ Foreign, 2 –Indian] 

In Category C Monuments, there will be 2 counters [1 - Information Kiosk/ Foreign, 1 –Indian] 

In Category D Monuments, the ticket issuance and validation will be done using mobile device 

All the counters although specified however will also act as a ticket issuance counter as and when the need arises 

Bill of Quantity 

Name Quantity 

Total Monuments 116 

Total Manpower Required 984 

Total PCs 179 

Total Handheld Devices 131 

Total Printers 85 

Total Scanners 186 



Visitor Footfall Details 

Tourist Inflow at Centrally Protected Ticketed Monuments 

S.NO NAME OF 

MONUMENTS 

Agra Circle 

2009-10 2010-11 2011-12 2012-13 


(April – November) 

Indian Foreign Indian Foreign Indian Foreign Indian Foreign 

1. Taj Mahal 2970221 581418 4181228 650205 4777445 699936 4117325 489572 

2. Agra fort. 1447226 383025 1437513 339146 1651182 319852 1289818 221566 

3. Fatehpur Sikri 303191 179291 330941 214391 435570 244626 362150 172814 

4. Akas To, 

Sikandara 

5. Maias To, 

Sikandara 

289858 40942 442425 54898 471751 61682 402330 36704 

11120 162 290269 248 31246 274 30415 246 

6. Itimad-ud-Daulah 66376 43705 87933 55840 123475 71258 132080 49629 

7. Ram Bagh 26624 221 34527 326 53295 5851 47347 213 

8. Mehtab Bagh 32562 6794 67848 14453 94069 18602 76040 15256 

Total 

Aurangabad Circle 

5147178 1235558 6872684 1329507 7638033 1422081 6457505 98600 

9. Ajanta Caves 90602 3301 388230 27827 411193 29132 322488 15054


S.NO NAME OF 

MONUMENTS 

2009-10 2010-11 2011-12 2012-13 




10. Ellora Caves 189920 2361 1185607 32276 1330506 33954 1096386 17954 

11. Bibi ka Maqbara 1054041 14528 1788463 17274 1235380 15141 988648 8652 

12 Daulatabad Fort 442721 7789 811145 10679 635498 9211 474948 4938 

13. Pandulena Caves 120641 908 228837 1060 185000 1166 166630 642 

14. Aurangabad Caves 38745 2056 71670 2376 47926 2190 33537 1317 

Total 

Bangalore Circle 

15. World Heritage Site, 

Hampi 

16. Daria Daulat Bagh, 

Sriragapatna 

17. Keshva Temple 

Somanathpur 

1936670 30943 4473952 91492 3845503 90794 3082637 48557 

445521 33807 432602 34217 451518 38387 368490 19206 

791645 25797 1726831 40190 933252 27063 669882 14425 

174271 11613 366562 84611 200077 31180 117800 7173 

18. Tippu Palace Bangalore 118274 5376 295372 12528 160966 7089 102205 3681 

19. Chitradurga Fort 

Chitradurga 

259461 494 583721 789 354182 696 290254 381


S.NO NAME OF 

MONUMENTS 

2009-10 2010-11 2011-12 2012-13 




20. Bellary Fort, Bellary 6417 19 13048 281 5501 64 5774 33 

Total 

Bhopal Circle 

21. Buddhist Caves 

22. The Palace Situated, 

Burhanpur 

23. Bhojshala and Kamal 

Maulas osue 

24. Hoshangs Tomb, 

Mandu 

1795589 77106 3418136 172616 2105496 104479 1554405 44899 

23912 17 34972 26 15813 17 12926 8 

68049 181 87318 174 52560 212 47700 154 

15215 0 23291 0 11423 0 9032 0 

147668 2523 257411 2243 164751 2213 143527 1402 

25. Royal Palaces, Mandu 250953 2806 420670 2530 262164 2532 238991 1596 

26. Roopmati Pavilion 264758 2376 468270 2184 283322 1996 253039 1333 

27. Western Group of 

Temple, Khajuraho 

228361 81666 248943 93639 245595 97738 186729 57399 

28. Buddhist monuments, 

Sanchi 

175453 6540 201187 6955 207421 6035 151426 3094 

29. Gwalior Fort. 205127 13827 348445 18084 256105 14629 201599 7852 

Total 1379496 109936 2090507 125835 1499154 125372 1244969 72838


S.NO NAME OF 

MONUMENTS 

Bhubaneswar Circle 

2009-10 2010-11 2011-12 2012-13 




30. Sun Temple Konark 1863767 8644 2254645 8505 2230683 9137 1613574 4593 

31. Udayagiri & Khandagiri 

Sites 

378889 3393 550046 3551 442952 3668 287984 1698 

32. Rajarani Temple 28153 1884 37491 1853 28710 2294 16267 754 

33. Ratnagiri Monument 

26927 503 40743 410 22938 628 24671 279 

34. Lalitagiri Monument 11716 308 16569 339 16893 481 11749 186 

Chennai Circle 

Total 2309452 14732 2899494 14658 2742176 16208 1954245 7510 

35. Group of Monument, 

Mamallapuram 

955476 67003 985537 64099 1012422 73619 736253 41956 

36. Front Museum, 

Thirumayam 

60344 1017 170541 2934 65573 1440 33539 486 

37. Gingee Fort, Gingee 161131 3577 268072 4463 154492 3281 120316 2520 

38. Fort on Rock, Dindigul 38326 133 60711 567 27963 67 22141 97 

39. Moovarkoil 

Kodambalur 

420 23 5426 228 6925 68 783 23


S.NO NAME OF 

MONUMENTS 

40. Rock Cut Jain Temple, 

Sittanasal 

2009-10 2010-11 2011-12 2012-13 




14505 219 37070 372 32826 335 23806 122 

41. Natural Caven with 

Insription Eladipattam, 

Sittannavasal 

14070 101 36336 594 33248 273 17880 31 

Total 1244272 72073 1563693 73257 1333449 79083 954718 45235 

Chandigarh Circle 

42. Sheikh Chilli's Tomb 

Thanesar 

119433 155 161800 97 108680 138 94484 82 

43. Suraj Kund, Faridabad 30654 65 47674 102 35170 116 19174 60 

Dharwad Circle 

Total 150087 220 209474 199 143850 254 113658 142 

44. Durga Temple Complex, 

Aihole 

187515 4614 347846 5470 233713 4745 173467 2421 

45. Jaina & Vaishnava 

Caves, Badami 

364143 7420 687626 8515 444178 7197 320343 3533 

46. Group of Monuments 255214 5682 294392 5819 334237 6025 242063 2968


S.NO NAME OF 

MONUMENTS 

(WH), Pattadakal 

2009-10 2010-11 2011-12 2012-13 




47. Gol-Gumbaz, Bijapur 953462 3019 1994006 3419 1079414 2945 826077 1598 

48. Ibrahim Rouza, Bijapur 164443 2235 333723 2592 240712 2286 173647 1231 

49. Temple and Sculpture 

Shed, Lakkundi 

13531 219 18936 161 13836 319 11476 93 

Total 1938308 23189 3676529 25976 2346090 23517 1747073 11844 

Delhi Circle 

50. Jantar Mantar 320737 9626 365919 11959 489734 15326 352727 9577 

51. Khan-I-Khana 8298 95 8828 744 15486 280 10595 170 

52. Purana Qila 593074 8042 542417 10512 753314 25235 520095 5574 

53. Sultanghari Tomb 375 100 330 0 330 0 526 24 

54. Tughluqabad 21425 1451 28211 1537 42789 1648 36118 1031 

55. Kotla Feroz Shah 52380 555 47892 624 71008 891 54615 653 

56. Safdarjung Tomb 49940 5275 57717 7044 78390 7349 64226 4108 

57. Red fort 2398783 141516 2292110 144667 2687367 166782 2227732 108984 

58. Humayun's Tomb 309186 208490 406373 232341 528622 263780 788881 184215 

59. Qutb Minar Day 2297296 262125 2591538 295159 3057616 339993 2502412 230550 

Total 6051494 637275 6341335 704587 7724656 821284 6557927 544886


S.NO NAME OF 

MONUMENTS 

Guwahati Circle 

60. Aho ‘ajas Palae, 

Garhgaon, Distt. 

Sibsagar 

61. Karenghar of Ahom 

Kings, Sibsagar 

62. Ranghar pavillion, 

Jaisagar. 

2009-10 2010-11 2011-12 2012-13 




38713 73 46876 94 49082 86 31401 107 

129627 437 180856 416 167815 470 87039 332 

61609 344 69259 322 62731 376 40297 236 

63. Bisnudol, Joysagar. 9929 14 15313 19 13410 56 7543 23 

64. Group of four Maidams 

Charaideo, Distt. 

Sibsagar 

Total 

Hyderabad Circle 

33883 24 38224 14 37393 19 13992 12 

273761 892 350528 865 330431 1007 180272 710 

65. Charminar 1136508 5552 2258366 24487 1455608 13329 1187467 8226 

66. Golconda 104554 675 2088398 19363 1478094 19125 1242039 14117 

67. Amaravathi 1160 5 119698 151 17771 219 13107 111


S.NO NAME OF 

MONUMENTS 

2009-10 2010-11 2011-12 2012-13 




68. Nagarjunakonda 2294 18 135162 671 131846 631 67577 531 

69. Undavalli 2912 19 82219 535 70847 421 51229 244 

70. Guntuplli 629 0 11279 39 19268 26 18060 6 

71. Warangal 5357 12 140618 410 111420 307 84898 230 

72. Chandragiri 7164 3 165789 208 102910 108 76807 60 

Total 

Jaipur Circle 

1260578 6284 5001529 45864 3387764 34166 2741184 23525 

73. Chittaurgah Fort 377291 18795 734003 21096 492913 21618 411853 12001 

74. Kambhalgarh Fort 

Distt.Rajmand 

75. Deeg Palace Deeg Distt. 

Bharatpur 

Total 

138774 17742 225591 20430 174289 18561 158316 12440 

28766 1241 74537 1475 34013 1081 34495 663 

544831 37778 1034131 43001 701215 41260 604664 25104


S.NO NAME OF 

MONUMENTS 

Kolkata Circle 

2009-10 2010-11 2011-12 2012-13 




76. Koch Bihar Palace 371247 46 738199 356 401181 73 296996 42 

77. Hazarduari Palace 600930 654 877753 417 696212 533 420541 368 

78. Bishnupur Gr. of 

Temples. 

Total 

Lucknow Circle 

84747 571 359862 35595 87789 862 63112 255 

1056924 1271 1975814 36368 1185182 1468 780649 665 

79. Sahet Sravasti 60579 2883 36858 4317 151215 6723 108890 4653 

80. Jhansi Fort, Jhansi 132104 851 51908 254 298969 793 169480 426 

81. Rani Mahal, Jhansi 6588 53 4844 13 20589 70 11588 17 

82. Residency, 

137254 1394 70955 858 282491 2638 248807 2569 

Lucknow 

Total 336525 5181 164565 5442 753264 10224 538765 7665 

Mumbai Circle 

83. Elephanta Caves 299903 22187 119024 10501 375255 20873 362036 19528


S.NO NAME OF 

MONUMENTS 

2009-10 2010-11 2011-12 2012-13 




84. Kanheri Caves 101064 2536 44475 1117 186019 4948 148705 3227 

85. Shaniwarwada 372787 5474 94336 1948 743048 7700 383805 4985 

86. Agakhan Palace 83656 7635 26764 3268 103577 9481 75295 4251 

87. Lenyadri Caves 304696 218 84410 44 367946 147 308144 79 

88. Karla Caves 127825 2112 48620 1045 210781 2154 147501 1275 

89. Bhaja Caves 26382 856 9418 413 46502 949 37173 720 

90. Raigad Fort 185963 168 57052 78 175990 184 235402 86 

91. Kolaba Fort 62374 93 22156 88 55158 212 25278 65 

92. Sholapur Fort 25000 6 4225 6 14743 16 9633 9 

Total 

Patna Circle 

93. Remains of Patliputra, 

Kumrahar 

94. Ancient Site of Vaishali, 

Kolhua 

1589650 41285 510480 18508 2279019 46664 1732972 34225 

90453 713 84670 861 95853 469 84641 310 

96883 7112 94458 5789 139375 8255 85411 5451


S.NO NAME OF 

MONUMENTS 

95. Excavated Remains at 

Nalanda 

96. Ruins of Vikramshila, 

Antichak 

97. “he “hah “uis To, 

Sararam 

98. Old fort (Shahi fort), 

Jaunpur 

99. Lord Cornwallis Tomb, 

Ghazipur. 

100. Observatory Man Singh 

(Man Mahal), Varanasi. 

2009-10 2010-11 2011-12 2012-13 




223043 61018 237436 55003 516135 23114 386925 13701 

130510 104 134681 128 50449 4633 35610 251 

5037 127 5310 430 215651 328 149522 128 

383623 15150 423220 19523 176727 234 145707 119 

152561 201 178205 262 19084 12 18271 2 

10931 113 17267 7 5869 454 5159 379 

101. Excavated Remains at 

Sarnath 

30176 308 44467 277 309174 80078 244689 44625 

Total 1123217 84846 1219714 82280 1528317 117577 1155935 64966 

Raipur Circle 

102. Laxman Temple 43716 38 18143 28 42901 15181 23848 36 

Total 

43716 38 18143 28 42901 15181 23848 36


S.NO NAME OF 

MONUMENTS 

Shimla Circle 

2009-10 2010-11 2011-12 2012-13 




103. Kangra Fort, Kangra 55966 1030 13868 397 84186 1641 62186 1433 

104. Rock- Cut Temple, 

Masroor 

Total 

Srinagar Circle 

105. Palace Complex at 

Ramnagar, District 

Udhampur 

106. Group of Temples at 

Kiramchi, District 

Udhampur 

107. Avantiswamin Temple, 

Avantipur, District 

Pulwama 

108. Ancient Palace at Leh, , 

District Leh 

Total 

15021 401 4691 88 21527 934 17406 699 

70987 1431 18559 485 105713 2575 79592 2132 

2450 1 2777 1 3436 0 3252 9 

1471 0 2430 1 2969 0 2870 0 

8048 36 7721 27 18442 94 26154 175 

6295 4019 10500 4700 0 0 

18264 4056 23428 4729 24847 94 32276 184


S.NO NAME OF 

MONUMENTS 

Thrissur Circle 

109. Bekal Fort, Pallikkare, 

Distt. Kasargod 

110. Mattancherry Palace 

Museum, Kochi, Distt. 

Ernakulam 

Vadodara Circle 

2009-10 2010-11 2011-12 2012-13 




145755 337 238065 484 310273 673 267057 608 

173352 145548 147220 85610 224775 129318 172992 77394 

Total 319107 145885 385285 86094 535048 129991 440049 78002 

111. Jami Masjid, 

Champaner- Pavagadh 

Saher ki Masjid 

Champaner Pavagadh 

102173 1404 75747 2165 115834 2095 85221 1008 

112. Sun Temple, Modhera 206837 2405 57389 1072 309215 3369 270328 1789 

113. Rani-ki-Vav, Patan 217125 2123 18592 924 273203 2906 242113 1366


S.NO NAME OF 

MONUMENTS 

114. Ashokan Rock Edicts, 

Junagadh 

115. Buddhist Caves, 

Junagadh 

2009-10 2010-11 2011-12 2012-13 




47678 491 9474 254 36841 631 30837 308 

56609 762 13650 381 54382 852 43800 541 

116. Baba Pyara Caves, 

Junagadh & Khapra 

Khodiya Caves, 

Junagadh 

303 4 98 4 557 45 556 18 

Total 630725 7189 174950 4800 790032 9898 672855 5030 

Grand Total 29220831 2537168 42422930 2866591 41042140 3093177 32650198 1116755


Technical Specifications 

The specification and BOM provided below is indicative. The bidder should provide the complete BOM 

in the technical proposal (without price). The same BOM along with prices shall be provided in the 

commercial proposal. The BOM in the technical bid should match the BOM submitted in the 

commercial bid. 

Specifications of each component: 

The indicative general configurations for the server and other are provided below. The specifications 

are indicative and the Successful Bidder must fine-tune and provide detailed specifications and 

numbers as per requirements of the system proposed. 

The Successful Bidder should also propose the specifications of any additional servers and other 

hardware, if required for the system. 

Features common for all hardware items 

All components shall be rated for continuous operation. 

Availability of spares and support for the system for the complete period of the contract. 

The Bidder shall provide all other H/W items that are not explicitly mentioned herein but are 

required to fulfill the intended specifications by the Bidder in the bid. 

The Specifications parameters are indicative and any item of higher rating will be preferred. 

All servers (systems) shall be of same make. 

No item should be offered whose end-of-sale has been declared by the OEM or has been 

declared to be under phase out. 

All events and changes applied to the device configurations shall be audited and logged. 

The proposed devices shall provide support for alerting the solution and also provide support 

for syslog and SNMP. 



S.No Blade Chassis Specifications Compliant 

(Yes/No) 

1. Single blade chassis should accommodate 

minimum 6 or higher hot pluggable blades 

2. Should accommodate x86 based processor 

Blade Servers 

3. DVD ROM can be internal or external, which can 

be shared by all the blades allowing remote 

installation of S/W and OS 

4. Minimum 2 external USB connections 

functionality 

5. Hot-plug, redundant Gigabit Ethernet switch 

module with minimum 10 ports (cumulative), 

which enable connectivity to Ethernet via switch. 

6. Hot Swap redundant power supplies to be 

provided 

7. All Power Supplies modules should be populated 

in the chassis 

8. Hot Swappable and redundant Cooling Unit 

9. Systems Management module for management 

and deployment tools to aid in Blade Server 

configuration and OS deployment locally as well 

as remotely. 

10. Remote console management capabilities 

11. Blade enclosure should have provision to 

connect to display console / central console for 

local management like trouble shooting, 

configuration, system status/health display. This 

should be either wall and table mountable 

inclusive of stand 

Remarks 



S.No. Blade Server Specifications Compliant 

(Yes/No) 

1. Blade can be half / full height with I/O 

connectivity to backplane 

2. 2 * x86 based 8 core processor or better having 

specint rate of 630 or more 

3. Min 8 GB DDR-III ECC Memory with min free slots 

for future expandable capability. 

4. Minimum Memory: 8 GB scalable to 64 GB per 

blade 

5. The Blade should have redundant 4 Gbps Fiber 

Channel HBA/ ports to connect to storage 

6. 2 X (1000BASE-T) Tx Gigabit LAN ports with TCP / 

IP offload engine support / dedicated chipset 

for network I/O on blade server 

7. 2 X 300 GB SAS HDD or more hot swappable/ hot 

pluggable system disk with mirroring using 

integrated RAID 0,1 on internal disks. It should be 

possible to hot swap the drives without shutting 

down the server. 

8. Should support heterogeneous OS platforms 

9. VGA / Graphics Port / Controller 

10. The blade should support for virtualization using 

the operating system proposed 

11. For Management of the blade servers, Blade 

Server OEM management software to be 

provided with device drivers 

Remarks 



Desktop: May please note that the non-stadard ad asseled PC’s shall ot e aepted 

Desktop specifications 

Features Specifications Compliant (Y/N) Remarks 

Processor, 

Chipset & 

Mother 

Board 

RAM 

Hard Disk 

Drive & 

controller 

Latest Generation CPU 3.10 

Ghz or higher, 6MB Cache and 

Standard OEM Chipset and 

Mother Board. 

4 GB DDR3 PC3- 6400 (1066 

Mhz) Non ECC RAM 

expandable up to 16 GB (4 

DIMM Slots minimum) 

500 - GB SATA 3.0 Gb/s Hard 

Drive (16 MB Cache, 7200 

RPM with SMART or 

equivalent technology for 

self-monitoring and prefailure 

alert) 

Optical Drive Internal DVD-ROM / RW 

Graphics and 

Audio 

Ethernet 

Bays 

Slots 

Ports 

Integrated Graphics and 

Audio 

Gigabit 10/100/1000 Network 

card with remote booting 

facility 

External : 2 * 5.25" drive bays 

; Internal : 2* 3.5" drive bays 

Minimum 3 PCI / PCI express 

slots 

Ports :Minimum 6 * USB 3.0 

(some in rear and some in 

front) , 1 Serial Port, 1 

Parallel Port, 1 mike in , 1* 

VGA, 1* Line in , 1* Line out, 

1* RJ 45 



Power Supply 

Keyboard 

Monitor 

Mouse 

Operating 

System 

Office 

Productivity 

Compliance 

and 

Certifications 

Drivers 

Minimum 300-watt ATX 

Power Supply – PFC (Active 

Power Factor Correction (PFC) 

power supply). Surge 

Tolerance of up to 2000V 

USB/PS/2 104 keys keyboard 

(Same make as PC) 

8. LCD oito ith TCO 

5.0 Certification, Energy Star 

USB/PS/2 2 Button Optical 

Scroll Mouse(Same make as 

PC) 

Windows7 or Equivalent or 

Linux (latest release) 

Complete Office Productivity 

As per industry standard for 

PC and energy star for 

Monitor 

Drivers should be freely 

aailale o OEMs esite 

and should be supplied in 

media along with the PC 

Certifications Windows Or Equivalent 

Warranty 

Antivirus 

5 years comprehensive onsite 

replacement warranty from 

the date of acceptance of 

systems as per the other 

clauses of the RFP 

For each PC with upgrade 

license for 5 years (CDs to be 

included) 



Data Centre and Disaster Recovery Bill of Materials: 

Item Description Qty Compliance 

Data Centre Server Components 

Application Server No. (s) to be 

Database Server 

ascertained and 

provisioned by 

Web Server 

IA 

Authentication Server 

Any other server, please mention 

Software 

Operating System 

System Software 

EMS for SLA Measurement Tools and Application 

Performance management & monitoring 

Disaster Recovery Centre Server Components 

Application Server No. (s) to be 


ascertained and 

procured by IA 

Web Server 


Software 



EMS for SLA Measurement Tools and Application 

Performance management & monitoring 

Any other server, please mention 

Fibre Cabling and Network Items for Data Centre and Disaster Recovery Centre 

Internet Routers Shared service 

(Y/N) 


Remarks


Item Description Qty Compliance 

Core switch 

Application Switches 

UTM Firewall with VPN and IPS 

Server racks 

Host Intrusion Prevention System (HIPS) 

Patch Panel 

Building Monitoring System, Access Control, Physical 

Security & Surveillance, Power Supply, UPS Backup 

and Generator, Precision AC, Fire Prevention System, 

Enterprise Management System for Infrastructure 

Management (Servers) including network and ITIL 

based Helpdesk 

Data Centre and Disaster Recovery Centre Software 

Data Center Software (Server OS with CAL, Server 

Management etc.) 

as a part of DC 

rental 

To be ascertained 

and provisioned 

by IA 

SAN Storage Shared service as 

SAN Switch 

a part of DC 

rental 

Virtual Tape Library 

Bandwidth for DC and DR 

WAN connectivity for internet gateway (10 Mbps) 

Replication links between DC & DR (2 Mbps) 

Other(s) - please specify 

(Y/N) 


Remarks


Enterprise Management System 

EMS Features 

Basic Requirement : 

Solution should provide for future scalability of the whole system without major 

architectural changes. 

Should be SNMP compliant. 

Filtering of events should be possible, with advance sort option based on components, type 

of message, time etc. 

Should support Web / Administration Interface. 

Should provide compatibility to standard RDBMS. 

Solution should be open, distributed, and scalable and open to third party integration. 

Should provide fault and performance management for multi-vendor TCP/IP networks. 

Fault Management 

Should be able to get fault information in real time and present the same in alarm window 

with description, affected component, time stamp etc. 

Should be able to get fault information from heterogeneous devices routers, switches, 

servers etc. 

Event related to servers should go to a common enterprise event console where a set of 

automated tasks can be defined based on the policy. 

Should have ability to correlate events across the entire infrastructure components of 

DC/DR. 

Should support automatic event correlation in order to reduce events occurring in DC/DR. 

Should support advanced filtering to eliminate extraneous data / alarms in Web browser 

and GUI. 

Should be configurable to suppress events for key systems/devices that are down for 

routine maintenance or planned outage. 

Should be able to monitor on user-defined thresholds for warning/ critical states and 

escalate events to event console of enterprise management system. 

Should provide out of the box root cause analysis with multiple root cause algorithms 

inbuilt for root cause analysis. 

Should have self-certification capabilities so that it can easily add support for new traps and 

automatically generate alarms. 

Should provide sufficient reports pertaining to asset and change management, alarms and 

availability of critical network resources as well as network response times for critical links. 



The tool shall integrate network, server and database performance information and alarms 

in a single console and provide a unified reporting interface for network and system 

components. The current performance state of the entire network and system 

infrastructure shall be visible in an integrated console. 

Should provide an integrated performance view for all the managed systems and networks 

along with the various threshold violations alarms in them. It should be possible to drill- 

down into the performance view to execute context specific reports. 

Should provide the following reports for troubleshooting, diagnosis, analysis and resolution 

purposes: Trend Reports, At-A-Glance Reports, & capacity prediction reports. 

Should be able to auto-calculate resource utilization baselines for the entire managed 

systems and networks and allow user to set corresponding upper and lower threshold 

limits. 

Application Performance Management 

End to end Management of applications (J2EE/.NET based) 

Determination of the root cause of performance issues whether inside the 

Java / .Net application in connected back-end systems or at the network layer. 

Automatic discovery and monitoring of the web application environment 

Ability to monitor applications with a dashboard. 

Ability to expose performance of individual SQL statements within problem transactions. 

Monitoring of third-party applications without any source code change requirements. 

Proactive monitoring of all end user transactions; detecting failed transactions; gathering 

evidence necessary for problem diagnose. 

Storage of historical data is for problem diagnosis, trend analysis etc. 

Monitoring of application performance based on transaction type. 

Ability to identify the potential cause of memory leaks. 

Reporting 

Should able to generate reports on predefined / customized hours. 

Should be able to present the reports through web and also generate pdf / CSV / reports 

of the same. 

Should provide user flexibility to create his /or her custom reports on the basis of time 

duration, group of elements, custom elements etc. 

Should provide information regarding interface utilization and error statistics for physical 

and logical links. 

Should create historical performance and trend analysis for capacity planning. 

Should be capable to send the reports through e-mail to pre-defined user with pre-defined 

interval.


Should be able to generate all sorts of SLA Reports. 

Should be able to generate web-based reports, historical data for the systems and 

network devices and Near Real Time reports on the local management console. 

Should have capability to exclude the planned-downtimes or downtime outside SLA. 

Should be able to generate the reports for Server, Application. 

Provide Historical Data Analysis: The software should be able to provide a time snapshot 

of the required information as well as the period analysis of the same in order to help in 

projecting the demand for bandwidth in the future. 

Application 

Availability Reports 

Availability and Uptime – Daily, Weekly, Monthly and Yearly Basis 

Trend Report 

Custom report 

MTBF and MTTR reports 

SLA Monitoring: 

The SLA Monitoring component of EMS will have to possess the following capabilities: 

EMS should integrate with the application software component of portal software that 

measures performance of system against the following SLA parameters: 

o Response times of Portal; 

o Uptime of IT Infrastructure; 

o Meantime for restoration of services etc. 

EMS should compile the performance statistics from all the IT systems involved and 

compute the average of the parameters over a quarter, and compare it with the SLA 

metrics laid down in the RFP. 

The EMS should compute the credits/debits of the SLA metrics and arrive at the quarterly 

service charges payable to the Agency after applying the system of penalties and rewards. 

The SLA monitoring component of the EMS should be under the control of the authority 

that is nominated the client so as to ensure that it is in a trusted environment. 

The SLA monitoring component of the EMS should be subject to random third party audit 

to vouchsafe its accuracy, reliability, and integrity. 



Ticket Printer 

Feature Specification 

Communication 

Interface RS-232, Parallel, USB, Ethernet 

Printing method Direct Thermal & Thermal Transfer 

Printing resolution 200 to 300 DPI 

Printing Length 10cm to 15cm 

Printing Length 3-4 Tickets per second 

Printing Width 4 to 5cm 

Memory 8 to 10 DRAM, 4 to 5 FLASH ROM 

Sensors Media Gap, Black Line 

2D Barcodes MaxiCode, QRCode, Composite Code 

1D Barcodes Code 39, Code 93, Code 128 A,B,C 

Storage Temperature 0C to 50C 

Operation Temperature 4C to 40C 

Media Type Roll-feed, die cut, continuous, fan-fold, tags, ticket in thermal paper 

Printer Type Desktop 

Graphics BMP, IMG, GIF 

Ticket Scanner 

Feature Specification 

Weight 200 to 300grams 

Number of Scans per full charge 10,000 to 20,000 

Mounting Position Horizontal or Vertical 

Operation Temperature 4C to 40C 

Storage Temperature 0C to 50C 

Communication Interface RS-232, USB 

Cardless Yes 

Scan Elementry Frequency 50 to 100Hz 

Handheld Yes 

Radio Type Bluetooth or Other 

Radio Range 10 to 20Meters 

Scanner Technology Laser, Imager 

Scan Pattern Omni Directional 

Scan Capability 1D and 2D barcodes 



Proposed Process Diagrams (indicative) 

Web Based Online Ticketing Process 

Online Booking 

Capturing Details 

Payment 

Booking Confirmation 

Value Added Services 

Visitor End 

Internet 

Booking 

Notification 

Booking 

Retrieval 

ETS Application 

Fill Up Online form 

(Visitor Details , Special Needs, 

Monument Details, Date ,etc) 

Visitor & Monument Details 

Make Payments 

Confirmation Page 

Customer validation 

Payment Gateway 

Partner 

Store Visitor details 

(Foreign/Indian/Physically Challenged/ 

School Group/VVIP/Freedom Fighter) 

Trip Booking Confirmation 

Customer Authentication 

Customised Alerts & Notifications 

Database 

Repository 

Transaction 

Acknowledgement 

Reconciliation 



Ticket Issuance at Monument 

Ticket Issuance at POS 

Making Payment 

Verification 

ASI Website Dashboard 

MIS Reports & Performance 

Monitoring 

Ask for Printed 

Ticket 

Ticket Counter 

(Monument) 

SMS Notification 

Pre Booking 

Dashboard Monitoring 

Point of Sale 

Counter 

Handheld 

Device 

Ticket Generation 

Internet Ticket 

Sales / Revenue 

Data 

ETS-POS Application Validation/Approval 

Capture Visitor Details 

Verification at Gate 

25 25 

25 % 25 % 

% % 

ASI Website 

1 

2 

Credit Card 

Payment 

Currency Cash Deposit 

Chest 

Real Time Data Reconciliation 

3 

Transaction Partner 

Approval 

Reconciled 

Records 


Status 

Update 

Database 

Repository 

Processed for 

Invalidation 

Reconciled data 


4 

5 

Entry of Ticket Sales 

in POS System 

Store Visitor Data 


of POS & Web

RFP for e-ASI Project Volume-II 

Request for Proposal 

e-Ticketing Solution 

For Archaeological Survey of India, Volume-II 

Commercial and Bidding Terms 

March 2013 

Submitted by 

National Institute for Smart Government 

April 2013

RFP for e-Ticketing Solution Volume-II 



1. Introduction ................................................................................................................................... 8 

2. Scope of Work for Implementation Agency (IA) ............................................................................ 9 

3. Constitution of the Team ............................................................................................................. 10 

3.1 OVERVIEW OF THE TEAM FOR IMPLEMENTATION OF THE APPLICATION .............................................. 10 

3.2 TEAM STRUCTURE ....................................................................................................................... 10 

3.3 PERSONNEL PROFILE .................................................................................................................... 11 

3.3.1 Program Manager ......................................................................................................... 11 

3.3.2 Manager – Infrastructure ............................................................................................. 12 

3.3.3 Business Analyst ........................................................................................................... 12 

3.3.4 Solution Architect (Application Software) .................................................................... 13 

3.3.5 Database Administrator................................................................................................ 14 

3.3.6 Support Manager - Post Implementation ..................................................................... 14 

3.3.7 Support Executive - Post Implementation .................................................................... 15 

3.3.8 Operations Manager – On Site ..................................................................................... 15 

3.3.9 Staff – Ticket Issuance and Verification – POS ............................................................. 16 

3.4 GENERAL INSTRUCTIONS FOR PROPOSING THE TEAM ......................................................................... 16 

4. Approach & Methodology for Implementation of Technical Solution ........................................ 18 

5. Payment Terms & Schedule ......................................................................................................... 21 

6. Bidding Process Details ................................................................................................................ 24 

A. BIDDING SCHEDULE ..................................................................................................................... 24 

B. GENERAL INSTRUCTION TO BIDDERS ............................................................................................... 25 

C. BID SUBMISSION INSTRUCTIONS .................................................................................................... 30 

D. BID OPENING & EVALUATION PROCESS .......................................................................................... 34 

I. Evaluation of Prequalification Bid ..................................................................................... 35 

II. Evaluation of Technical Bids .............................................................................................. 35 

III. Evaluation of Commercial Bids .......................................................................................... 36 

IV. Rejection Criteria ............................................................................................................... 37 

7. Award of Contract ........................................................................................................................ 39 

A. POST QUALIFICATION AND AWARD CRITERIA ................................................................................... 39 

B. PURCHASER'S RIGHT TO VARY SCOPE OF CONTRACT ......................................................................... 39 

C. PURCHASER'S RIGHT TO ACCEPT AND REJECT BIDS ........................................................................... 39 

D. NOTIFICATION OF AWARD ............................................................................................................ 39 

E. NEGOTIATIONS WITH THE SUCCESSFUL BIDDER ................................................................................. 40 

F. SIGNING OF CONTRACT ................................................................................................................ 40 

G. PERFORMANCE SECURITY ............................................................................................................. 40 

Annexure 1: Bid Formats ....................................................................................................................... 41 

A. COVER LETTER ............................................................................................................................ 41 

B. PRE-QUALIFICATION LETTER ......................................................................................................... 44 

C. SUPPORTING INFORMATION FOR PRE-QUALIFICATION CONDITIONS .................................................... 46 

Archaeological Survey of India, Ministry of Culture Page 2 of 79


D. TECHNICAL BID FORMATS ............................................................................................................. 51 

i. Technical Bid Letter ........................................................................................................... 51 

ii. Credential Format.............................................................................................................. 53 

iii. Overview of Proposed Solution ......................................................................................... 54 

iv. Manpower details ............................................................................................................. 55 

E. COMMERCIAL BID LETTER ............................................................................................................. 57 

i. Price Bid format - Breakdown of Cost Components .......................................................... 59 

F. EVALUATION OF TECHNICAL BIDS ................................................................................................... 74 

Annexure 2: Request for Clarification Format ....................................................................................... 78 

A. FORMAT FOR CLARIFICATIONS ....................................................................................................... 78 

B. CLARIFICATION ON RFP DOCUMENT .............................................................................................. 78 

List of Tables 

Table 1 : Key Resource Requirements .................................................................................................. 11 

Table 2 : Progressive Roll-out Approach ............................................................................................... 18 

Table 3 : Project Implementation Schedule .......................................................................................... 20 

Table 4 : Terms of Payment for IA ........................................................................................................ 21 

Table 5 : Important Dates for Bid Process ............................................................................................ 24 







HR Human Resources 



NIC National Informatics Centre 






VPN Virtual Private Network over Broad Band 





About this Request for Proposal 

This document constitutes the Request for Proposal (RFP) for selection of Implementation 

Agency (IA) by Archaeological Survey of India (ASI). This RFP has been prepared to invite 

bidders to submit their proposals to implement and maintain e-Ticketing Solution. 

Information used for the preparation of this RFP has been made available from relevant and 

published sources of information. Nonetheless, bidders are required to make informed 

evaluation and decision based on their judgment. 





This RFP comprises the following documents: 

Volume I: Functional, Technical and Operational Requirements 

Volume I of RFP brings out all the details of solution requirements of the e-Ticketing 

system. This volume also gives the details of the other requirements (functional, 

operational and technical) of the e-Ticketing project. 

Volume II: Instruction to Bidders and Bidding Terms and Conditions 

Volume II of RFP brings out details of the bidding process, bidding terms and conditions 

and all that may be needed by the bidders to understand bidding process. 

Volume III: Master Service Agreement and Service Level Agreement 

Volume III of RFP explains the contractual terms that will govern the project 

implementation and operation. This includes the draft Master Service Agreement and 

Service Level Agreement that ASI intends to sign with the successful bidder or the selected 

Implementing Agency. 

This Document is Volume II. 



Disclaimer 

This Request for Proposal (RFP) for Selection of Implementation Agency is issued by 

Archeological Survey of India under the Ministry of Culture, Government of India. 

Whilst the information in this RFP has been prepared in good faith, it is not and does not 

purport to be comprehensive or to have been independently verified. Neither ASI, nor any 

of its officers or employees, nor any of their advisers nor consultants accept any liability or 

responsibility for the accuracy, reasonableness or completeness of the information 

contained in the RFP, or for any errors, omissions or misstatements, negligent or otherwise, 

relating to the proposed e Ticketing Project, or makes any representation or warranty, 

express or implied, with respect to the information contained in this RFP or on which this 

RFP is based or with respect to any written or oral information made or to be made 

available to any of the recipients or their professional advisers and, so far as permitted by 

law and except in the case of fraudulent misrepresentation by the party concerned, and 

liability therefore is hereby expressly disclaimed. 

The information contained in this RFP is selective and is subject to updating, expansion, 

revision and amendment at the sole discretion of ASI. It does not, and does not purport to, 

contain all the information that a recipient may require for the purposes for making a 

decision for participation in this process. Each Party must conduct its own analysis of the 

information contained in this RFP, to correct any inaccuracies therein and is advised to carry 

out its own investigation into the proposed e Ticketing Project, the regulatory regime which 

applies thereto and by and all matters pertinent to this Project and to seek its own 

professional advice on the legal, financial and regulatory consequences of entering into any 

agreement or arrangement relating to this Project. ASI shall not be responsible for any 

direct or indirect loss or damage arising out of or for use of any content of the RFP in any 

manner whatsoever. 

This RFP includes certain statements, projections, targets and forecasts with respect to the 

Project. Such statements, projections, targets and forecasts reflect various assumptions 

made by the management, officers, employees, consultants, and experts of ASI, which (the 

assumptions and the base information on which they are made) may or may not prove to be 

correct. No representation or warranty is given as to the reasonableness of forecasts or the 

assumptions on which they may be based and nothing in this RFP is, or should be relied on 

as, a promise, representation or warranty. 

ASI shall be the sole and final authority with respect to qualifying a bidder through this RFP. 

The decision of ASI in selecting the Implementation Agency who qualifies through this RFP 

shall be final and ASI reserves the right to reject any or all the bids without assigning any 

reason thereof. ASI further reserves the right to negotiate with the selected agency to 



enhance the value through this project and to create a more amicable environment for the 

smooth execution of the project. 

ASI may terminate the RFP process at any time without assigning any reason and upon such 

termination ASI shall not be responsible for any direct or indirect loss or damage arising out 

of such a termination. 



1. Introduction 

Particulars of RFP 

1.1. This iitatio to Tede is fo Estalishig E Ticketing Solution (ETS) fo the 

selected ticketed Monuments of Archaeological Survey of India (ASI). 

1.2. Bidders are advised to study the RFP Document carefully. Submission of Tender 

shall be deemed to have been done after careful study and examination of the 

Tender Document with full understanding of its implications. Sealed offers prepared 

in accordance with the procedures enumerated in Section 6 of RFP Volume II should 

be submitted to Senior Administrative Officer at ASI, not later than the date and 

time laid down, at his/her address given in the Section 6 of RFP Volume II. 

1.3. The tender document can be obtained during working hours on all working days at 

the office address (as prescribed in Section 6) from the start date of sale of tender 

till the last date. The tender document can also be downloaded from ASI website 

(www.asi.nic.in). 

1.4. Tender fee of Rs. 10,000 (Rupees Ten Thousand Only) has to be paid at the time of 

purchasing the tender from the office address or if the document is downloaded, 

should be submitted along with the Bid Security at the time of Bid Submission. 

Tede fee should e i fo of Dead Daft da i fao of Director General, 

Ahaeologial “ue of Idia paale at Ne Delhi. Tede fee suitted the 

bidder shall be non-refundable. 

1.5. This Tender document is not transferable. 

1.6. Bid Security 

1.7. All bids must be accompanied by Bid Security of Rs. 50,00,000 (Rupees Fifty Lakhs 

Only). Bid Security is to be submitted in the form of Demand Draft or Bank 

Guarantee issued valid for at least 180 days from the date of opening of Technical 

Bid. The Dead Daft o Bak Guaatee should e i fao of Director General, 

Ahaeologial “ue of Idia ad paale at Ne Delhi. 



2. Scope of Work for Implementation Agency (IA) 

Statement of Work 

This RFP envisages the following components of work to be executed by a competent IA in 

order to fulfill the objectives of the proposed e ticketing systems: 

a. Study, design, customization testing, and deployment of a web-based e-ticketing system, 

integrated with payment gateway, to enable visitors to pre-book tickets on internet at 

their convenience. 

b. Supply, installation, configuration, customization,, integration, testing and 

commissioning of Point-of-Sale (POS) application at ticketed monuments that shall have 

a common back-end platform that integrates with a common solution. 

c. Procurement, installation, configuration and commissioning of client side IT and non-IT 

infrastructure 

d. Deployment of server side application including IT and non-IT infrastructure at the DC- 

DR that is either owned by the IA or through a third party arrangement by IA. 

e. Facilitate ASI in provisioning, configuration and commissioning of network links to all the 

identified monument sites of ASI that enables connectivity to the Data Center and 

Disaster Recovery Center 

f. Supply of manpower services to manage and operate the ticketing system at ticket 


g. Operation and Maintenance of the entire e- Ticketing System including Application, IT & 

Non-IT infrastructure for a period of five years from the date of final Go-Live 




3. Constitution of the Team 

The constitution of the team of the bidder has been defined below for the various activities 

associated with the Project. 

3.1 Overview Of The Team For Implementation Of The Application 

3.1.1 Bidders must propose suitable profiles to meet the eligibility conditions given 

below. 

3.1.2 Bidder must note that the Seven (7) positions described below shall be used for 

technical evaluation. 

3.1.3 Bidder is required to make an independent evaluation of all positions that are 

required to be filled in order to meet the requirements of the project. 

It is mandatory that the resource proposed for the key position should not change in 

the first six months of the project. If at all, the resource is changed, a suitable 

replacement shall be made available with information for approval to ASI. 

For all other categories of resources, except the Key Personnel, the details of 

proposed resources may be furnished by the Bidder at the time of contract 

finalization. 

3.2 Team Structure 

Key Resource requirements (Minimum) 

Project Management Team 

Program Manager One Program Manager with at least 10 years of 

experience in similar implementations 

Project Implementation Team 

Manager Infrastructure One Infrastructure Manager with at least 8 eas 

experience of at least two (2) implementations of 

Ticketing solutions, or Monitoring solutions, 

preferably for a Government of India department 

Business Analyst One Business Analyst with at least 8 eas 

experience 

Solution Architect Application Oe “olutio Ahitet ith at least eas 

experience in designing or solutioning of similar 

application software 

Database Administrator One Database Administrator with at least 5 years 

experience 

Project Operations Team – Post Implementation 

Support Manager Operations Manager ith at least eas 

experience handling multiple locations 

Support Executives Executives ith at least 2 eas epeiee 

handling similar project 

Manpower Deployment at POS 



Operations Manager – On Site Operations Manager – On Site with at least 5 

eas epeiee i aagig opeatios of a 

similar nature 

Ticket Issuance Staff The staff at the PO“ should hae 2 eas 

experience in managing end to end operations of 

ticket issuance, verification and collection of cash 

Ticket Verifying Staff The staff at the PO“ should hae 2 eas 

experience in managing end to end operations of 

ticket issuance, verification and collection of cash 

Table 1 : Key Resource Requirements 

3.3 Personnel Profile 

The required profile of the personnel mentioned above is as follows: 

3.3.1 Program Manager 

a. Profile 

(S)He must have a minimum of 10 eas epeiee in IT with a minimum 

of 5 years in Program Management. 

(S)He must preferably have qualifications in Project Management (e.g., 

PMP certified). 

(S)He should have extensive experience and proven expertise in 

managing similar multi module contracts of this type and complexity. 

b. Responsibility 

(S)He should be responsible for organizing, planning, directing, and 

coordinating the overall program effort. 

(S)He should be responsible for allocating resources to the project. 

(S)He should be responsible for conflict management, issue and dispute 

resolution. 

(S)He should participate in all fortnightly / monthly project meetings and 

project review meetings. 

(S)He should review quality of project deliverables to ensure compliance 

with the agreed quality measures and standards. 

(S)He should review the integration test plan for completeness and 

correctness. 

(S)He should prepare Performance Test Plan which would specify the 

business transactions that would be tested for performance. 

(S)He should have a thorough understanding and knowledge of the 

principles and methodologies associated with program management, 

vendor management, quality assurance metrics and techniques, and 

configuration management tools. 



(S)He should ensure compliance with the Terms and Conditions of the 

Contract and NDA signed with ASI. 

3.3.2 Manager – Infrastructure 

a. Profile 

(S)He must have a graduation degree in Engineering or MCA. 

(S)He must have a minimum of 8 years experience in IT with minimum 4 

years in delivery lead / technical lead positions. 


3.3.3 Business Analyst 

a. Profile 

(S)He should be responsible for the overall infrastructure and should be 

dedicated to this project for the entire duration of this implementation. 

(S)He should be responsible for organizing, planning, directing, and 

coordinating to ensure stable operations of the IT Infrastructure. 

(S)He should be responsible for developing, maintaining, supporting and 

optimizing key functional areas, particularly network infrastructure, 

server infrastructure, data communications and telecommunication 

systems. 

(S)He should have sound knowledge of platform solutions to support 

applications, including their integration with database, network, and 

storage solutions. 

(S)He should be responsible for scheduling and directing activities to 

resolve hardware and software problems. 

(S)He should be familiar with specialized solutions including, making 

appropriate use of intrusion detection / prevention, Virtual Private 

Network (VPN), firewalls, and all elements of network-level security. 

(S)He must have an overall IT experience of not less than 8 years as 

Business Analyst in IT industry. 

(S)He shall be atleast a B Tech or B.E or have a Masters degree in Business 

Administration 


(S)He should preferably have certification as a Business Analyst 

Responsibility 



(S)He should be the key resource for studying all redesigned workflows/ 

processes and identifying the critical workflows for the envisaged 

solution. 

(S)He should lead the requirement gathering exercise by conducting 

meetings with the various process owners and the Project Management 

Team. 

(S)He should have the ability to intelligently probe department personnel 

and study the processes to understand the challenges that need to be 

addressed through the application 

(S)He should work in collaboration with the Program Manager to ensure 

that the gathered requirements are in line with the Project Vision. 

(S)He should be able to identify the use cases for all processes 

(S)He should be most visible in the initial requirement gathering stage of 

the project 

3.3.4 Solution Architect (Application Software) 

a. Profile 

(S)He must have a graduation degree in Engineering or MCA or M. Tech. 

(S)He must have a minimum 5 years experience in Solution Architecture 

Design 


(S)He should be responsible for creating or selecting the most appropriate 

architecture for a system (or systems), such that it suits the business 

needs, satisfies user requirements, and achieves the desired results under 

given constraints. 

(S)He should create Overall technical design (System Design Document - 

SDD) of the system consisting of project standards, the functional design 

and the database design. 

(S)He should develop integration test cases and include these in 

integration test plan. These test cases should focus primarily on testing 

the interfaces of the modules. Each test case should be described along 

with the input and output data, and the results expected after each test 

case. 

(S)He should have a thorough understanding of the technical and quality 

standards. 

(S)He should be most visible during the requirements and design stages of 

a project lifecycle, but should proactively monitor the adherence of the 

implementation to the chosen architecture during all iterations. 



Should have sound knowledge of platform solutions to support 

applications, including their integration with database, network, and 

storage solutions. 

Should possess working knowledge in the enterprise architecture best 

practices, including, but not limited to, logical and physical data 

architectures, network communications, operating systems, applications, 

data base servers, application servers, web servers, server consolidation, 

server performance, middleware, etc. 

3.3.5 Database Administrator 

a. Profile 

(S)He must have a graduation degree in Engineering or MCA or M. Tech. 

(S)He must have a minimum 5 years experience in Database 

Administration 


(S)He should be responsible for building, maintaining, administering and 

supporting databases 

(S)He should be responsible is responsible for the performance, integrity 

and security of a database. 

(S)He should be responsible for installing and configuring database 

management software, translating database design and diagnosing 

database performance issues 

(S)He should be responsible for installing software upgrades, managing 

hardware upgrades and maintaining servers 

(S)He should be responsible for backup and recovery strategies. 

(S)He should create Overall technical design (System Design Document - 

SDD) of the system consisting of project standards, the functional design 

and the database design. 

3.3.6 Support Manager - Post Implementation 

a. Profile 

(S)He should have an experience of over 8-10 years in application 

maintenance and management 

(S)He must be qualified as a B.E./B.Tech, M.C.A, M.E./M.Tech from a 

reputed university. 

Should preferably have relevant certification in implementation/ 

maintenance 




(S)He should have a thorough understanding of the requirements of the 

application being implemented along with the dependencies. 

He should be familiar with the overall deployment of solution 

(S)He should manage the flow of work within the team and ensure 

optimum allocation of work amongst team members. 

(S)He should be responsible for controlling the overall maintenance of the 

applications. 

(S)He should coordinate with team for regular updates on the application 

(S)He should coordinate with the relevant Programmers, Business 

Analysts and Testing Engineers for Unit & System Testing. 

(S)He should be able to assist the relevant personnel in ensuring proper 

maintenance and regular backup of application data 

3.3.7 Support Executive - Post Implementation 

a. Profile 

(S)He should have an experience of over 2 years in IT infrastructure and 

management 

(S)He must be qualified as a Graduate (any) with relevant IT certifications 

in managing systems/networks/databases and application management 


(S)He should be familiar with the overall deployment of solution 

(S)He should be responsible for coordinating and facilitating the overall 

maintenance of the applications, systems, networks etc. 

(S)He should coordinate with the team for regular updates on the 

application 

(S)He should be able to assist the relevant personnel in ensuring proper 

maintenance and regular backup of application data 

3.3.8 Operations Manager – On Site 

a. Profile 

(S)He should have an experience of over 5 years in managing operations 

of a similar nature of work 

(S)He must be qualified as a Graduate in any discipline from a reputed 

university. 

(S)He Should have adequate knowledge to handle computers 



(S)He Should have relevant experience in managing systems, people in 

retail chains 

(S)He should be fluent in English, local language and Hindi will be a must 


(S)He should be responsible for managing the end to end operations of 

POS. 

(S)He will be responsible for customer service, inventory, customer 

complaints etc. 

(S)He will be responsible for the team managing the POS 

(S)He will be responsible to ensure smooth operations during peak hours 

and ensure proper resource allocations to manage large crowds 


(S)He should manage the flow of work within the team and ensure 

optimum allocation of work amongst team members. 

3.3.9 Staff – Ticket Issuance and Verification – POS 

a. Profile 

(S)He should have an experience of over 2 years in managing operations 

of a similar nature of work 

(S)He must be preferably minimum Diploma / Graduate holder in any 

discipline from a reputed university. 

(S)He Should have adequate knowledge to handle computers 

(S)He should be fluent in English, local language and Hindi shall be a must 


(S)He should be responsible for managing the end to end operations of 

POS. 

(S)he should be responsible for managing cash collections 

(S)He should be responsible for managing large crowds at the 

Monuments 

(S)He will be responsible for customer service, inventory, customer 

complaints etc. 


3.4 General instructions for proposing the team 

3.4.1 Bidder should provide adequate number of personnel, with a clear definition 

of the role and responsibility of each. 



3.4.2 Bidder should ensure that all the personnel identified for this project have 

high level of integrity. Bidder should undertake necessary due diligence to 

ensure that the personnel have high standard of trustworthiness. Bidder 

should obtain an undertaking from each of the personnel assigned and the 

same should be submitted to ASI as and when demanded by ASI. Any 

information needed for this activity by ASI should be provided immediately by 

Bidder. 

3.4.3 Bidder can offer more than one key personnel for a role to improve the 

quality of key personnel keeping in mind the terms of reference given in the 

RFP. 



4. Approach & Methodology for Implementation of Technical Solution 

Project Implementation Model 

The e-Ticketing project shall be designed, built and operated on an outsourced model 

wherein the pojets desig, customization, ticketing operations and operation & 

maintenance shall be outsourced to a private agency to be known as Implementation 

Agency and selected through a competitive bidding process subject of this RFP. This model 

is adopted to facilitate utilization of private resources and expertise for implementation and 

operation & maintenance and at the same time to retain ASIs otol oe the sste 

design (through conformance to RFP requirements), development (through conformance to 

standards) and operation & maintenance (through conformance to SLA). 

Progressive Roll-out Approach with Timelines 

The implementation of the application would be phased in progressively, covering 

successively different geographies and Monuments. A summary of the Approach for 

Implementation is provided below for better understanding of the Bidder. 

Table 2 : Progressive Roll-out Approach 



Heritage 

Monuments & 

Category A 

Monuments ) 


the Annexure) 



Monuments & 

Category A 

)Monuments 

Centralized 





Application 

Centralized 





Application 

T + 14 weeks 

T +26 weeks 






Annexures) 



Annexures) 



Annexures) 

Detailed Project Implementation Schedule 

Centralized 





Application 

Centralized 





Application 


application 

T + 36 weeks 

T + 46 weeks 

T + 52 weeks 



weeks) 



2. Site preparation and Procurement of hardware for core 

infrastructure of DC, DRC 



Archaeological Survey of India, Ministry of Culture Page 19 of 79 

T+6 

T+8 

T+9





Monuments 



Monuments 






Round 2 



locations 





locations 



T+10 

T+12 

T+14 

T+26 

T+26 

T+36 

T+ 36 

T+ 46 

12. e- Ticketing documentation and Project documentation T+46 



locations 




Support 

Table 3 : Project Implementation Schedule 

T+ 46 

T+52 

T+52 to 312 

*T - indicates the project kick-off date - Bidders are advised to study the implementation 

approach carefully and propose the technical solution based on the implementation 

appoah. It is epeted that fo go-lie of eah round, Bidder would provide, application 

hosting, enable client infrastructure. 



5. Payment Terms & Schedule 

Payments to the IA shall have two components - During implementation and EQI 

Payments 

S. No. Project Milestone Payment (percentage of total 

1. Implementation of Solution Go-Live for Round 1 

and Round 2 

2. Implementation of Solution Go Live for Round 3, 4 

& 5 

3. Total Operation & Maintenance Support 

A 

Post Implementation Phase including: 

Project Management 

Technical Support & Helpdesk 

Year 1 Operation & Maintenance Support 

B Year 2 Operation & Maintenance Support 

C Year 3 Operation & Maintenance Support 

D Year 4 Operation & Maintenance Support 

E Year 5 Operation & Maintenance Support 

Table 4 : Terms of Payment for IA 

Contract value) 

50 % of Infrastructure & 

Application Cost 

Balance 50 % of infrastructure & 

Application cost 

Equal Quarterly installments 






The e- Ticketing project shall follow a government led bought out model wherein IA 

will be required to finance all the expenses, capital and operational, related to their 

scope of work in this project. ASI shall pay them back all the above expenditure 

subject to certain terms and conditions described below: 


RFP for e-ASI Solution Volume-II 

a. The entire cost of design, customization, implementation, operation and 

maintenance of the e-Ticketing project shall be borne by the IA. 

b. The IA would be paid by ASI for the above expenditure strictly as per the rates and 

amounts quoted by the IA in their commercial proposal and agreed by ASI. 

c. Payment will be subject to strict adherence to SLA signed between ASI and IA and 

subject to SLA credit/ debit points calculated by the team designated by ASI for every 

quarter as per the agreed methods, processes and tools. 

d. Payment shall be subject to penalty adjustment, if any, revealed during the SLA 

credit/ debit calculation or otherwise. 

e. Cost of third party audits, if any, shall be borne by ASI. 

f. ASI will make all efforts to make payments to the Bidder within 45 days of receipt of 

invoice(s) and all necessary supporting documents. 

g. All payments agreed to be made by ASI to the Bidder in accordance with the Bid shall 

be inclusive of all statutory levies, duties, taxes and other charges whenever 

levied/applicable, if any, and ASI shall not be liable to pay any such levies/ other 

charges under or in relation to this Contract and/or the Services. 

h. No invoice for extra work/ change order on account of change order will be 

submitted by the Bidder unless said extra work /change order has been 

authorized/approved by the ASI in writing in accordance with Change Control 

Schedule. 

i. The Contract would be signed for a period of Six years that includes one year of 

implementation and 5 years of operations and maintenance. Based on the 

performance of the Implementation Agency, ASI may decide to extend the period of 

contract by 2 years. The Contract rates for the extended 2 years would be based on 

the rates of AMC for 4 th year and would be negotiable between the Bidder and the 

ASI. ASI is not bound to extend the contract period by two years. 

j. The Bidder needs to provide rationale for the commercial quotes provided. ASI holds 

the right to ask for an explanation of the rationale from the Bidder 

k. In the event of ASI noticing at any time that any amount has been disbursed wrongly 

to the Bidder or any other amount is due from the Bidder to ASI, ASI may without 

prejudice to its rights recover such amounts by other means after notifying the 



Bidder or deduct such amount from any payment falling due to the Bidder. The 

details of such recovery, if any, will be intimated to the Bidder. The Bidder shall 

receive the payment of undisputed amount under subsequent invoice for any 

amount that has been omitted in previous invoice by mistake on the part of ASI or 

the Bidder. 

l. All payments to the Bidder shall be subject to deductions of tax at source under 

Income Tax Act and other taxes, and deductions as provided for under any law, rule 

or regulation. All costs, damages or expenses which ASI may have paid or incurred, 

for which under the provisions of the Contract, the Bidder is liable, the same shall be 

deducted by ASI from any dues to the Bidder. All payments to the Bidder shall be 

made after making necessary deductions as per terms of the Contract and recoveries 

towards facilities, if any, provided by the ASI to the Bidder on chargeable basis. 



6. Bidding Process Details 

a. Bidding Schedule 

i. Name of the Purchaser: 


ii. Addressee and Address at which RFPs to be submitted: 

Senior Administrative Officer 



Phone: +91-11-23018583 

Fax: +91-11- 23018583 


iii. Latest time and date for receipt of RFP response 

On or before 1500 hours on 6 May, 2013 

iv. Date till which the response to the RFP should be valid: 

180 days from the date of opening of the Technical Bids 

v. Important dates: 

The following table provides information regarding the important dates 

of the bid process for this RFP: 

Activity Date 

Release of RFP (Request for Proposal) April 26, 2013 

Last date for submission of questions by bidders May 03, 2013 

Pre-Bid Conference May 07, 2013 

Response to bidder queries May 13, 2013 

Last date for submission of Bids May 23, 2013 

Pre- Qualification Bid opening May 24, 2013 

Date for opening of Technical Bids for qualified bidders To Be Announced 

Date for Technical Presentations or Proof of Concept To be Announced 

Date for opening of Commercial Bids for qualified bidders To be Announced 

Award of Contract To be Announced 

Table 5 : Important Dates for Bid Process 

vi. Bidders must note that bids received after due date and time shall be 

rejected. The bids shall be submitted in the sealed box kept in the office of 



the Senior Administrative Officer at the addess etioed i this Section 

above. 

b. General Instruction to Bidders 

i. Cost of Bidding Process 

ii. Bid Prices 

1. The Bidder shall bear all costs associated with the preparation and 

submission of its bid, including cost of presentation for the purposes 

of clarification of the bid, if so desired by ASI. 

2. ASI will in no case be responsible or liable for the above mentioned 

costs, regardless of the conduct or outcome of the Tendering process. 

1. The Bidder shall indicate in the proforma prescribed at Annexure 1Di 

of Volume 2, the unit rates and total Bid Prices of the goods and 

services, it proposes to provide under the Contract. Prices should be 

shown separately for each item as detailed in Bid Documents. 

2. In the absence of information as requested in the above point a bid 

shall be considered incomplete and summarily rejected. 

3. The Bidder shall prepare the bid based on details provided in the RFP 

documents. The Bidder shall carry out all the tasks in accordance with 

the requirement of the RFP documents and it shall be the 

responsibility of the Bidder to fully meet all the requirements of the 

RFP documents. 

4. The Bidder as part of its Commercial Bid should account for all out of 

pocket and other expenses that the Bidder shall incur during the 

contract period. 

5. It is mandatory that Unit rates should be indicated in the Table as per 

the proforma prescribed at Annexure -1Di of Volume 2 of this RFP. 

This may be used by ASI for any changes to scope. 

iii. Firm Prices 

1. Prices quoted must be firm and final and shall remain constant 

throughout the period of the contract and shall not be subject to any 

upward modifications, on any account whatsoever. The Bidder shall, 

therefore, indicate the prices in Annexure – 1Di of Volume 2 



enclosed with the Bid. The Bid Prices shall be indicated in Indian 

Rupees (INR) only. 

2. The Commercial bid should clearly indicate the price to be charged 

without any qualifications whatsoever and should include all taxes 

(sales, service, etc.), duties (excise & customs, etc.), Octroi, fees, 

levies, works contract tax and other charges as may be applicable in 

relation to the activities proposed to be carried out. It is mandatory 

that such charges wherever applicable/payable should be indicated 

separately in Annexure – 1Di of Volume 2. 

3. A proposal submitted with an adjustable price quotation or 

conditional proposal shall be treated as non-responsive and the bid 

shall be rejected summarily. 

iv. Discount 

v. Bidder Authorization 

1. The Bidders are advised not to indicate any separate discount. 

Discount, if any, should be merged with the quoted prices. 

Discount of any type, indicated separately, will not be taken into 

account for evaluation purpose. 

1. The "Bidder" shall mean the one who has signed the RFP Form. 

2. The Bidder may be either the Principal Officer or his/her duly 

Authorized Representative, in which case he/she shall submit a 

power of attorney with the RFP response. All certificates and 

documents (including any clarifications sought and any 

subsequent correspondences) received hereby, shall, as far as 

possible, be furnished and signed by the representative. 

3. It is further clarified that the individual signing the tender or other 

documents in connection with the RFP must certify whether 

he/she signs as : 

Constituted attorney of the firm, if it is a company 

OR 

The Principal Officer or his/her duly Authorized Representative 

of the Bidder 



4. The authorization shall be indicated by power-of-attorney 

accompanying the bid. 

vi. Particulars for Bid Security 

1. The Bidder shall furnish, as part of its bid, a bid security of the 

amount mentioned in Section 1 of this volume of RFP. 

2. The bid security shall be denominated in Indian Rupees, and shall 

be in the form of a demand draft / Bank Guarantee issued by a 

Nationalized / Scheduled Bank 

3. No Bidder is exempted from furnishing of bid security. If a bidder 

is disqualified during the pre-qualification stage, their bid security 

shall be discharged/ returned after the pre-qualification results 

are declared. 

4. Usuessful Biddes id seuit ill e dishaged/ etued 

after award of contract to the successful Bidder. No interest will 

be paid by ASI on the Bid security amount. 

5. The suessful Biddes id seuit ill e dishaged upo the 

Bidder executing the Contract, and furnishing the performance 

security, pursuant to Section 6 of Volume 2 of this RFP. 

6. The bid security may be forfeited: 

a. if a Bidder withdraws its bid during the period of bid 

validity specified by the Bidder in the Bid; or 

b. in the case of a successful Bidder, if the Bidder fails: 

to sign the Contract 


or 

to furnish performance security in accordance 

vii. Period of Validity of Bids 

1. Bids shall remain valid for period as stated in Section 1 of Volume 2 

of this RFP. A bid valid for a shorter period shall be rejected by ASI 

as non-responsive and shall not be taken up for evaluation 

purposes. 

2. ASI may request the Bidder(s) for an extension of the period of 

validity. The request and the responses thereto shall be made in 

writing (or by e-mail or fax). The validity of bid security provided


viii. Revelation of Prices 

under Section 1 in Volume 2 of this RFP shall also be suitably 

extended. 

1. Prices in any form or by any reason before opening the Commercial 

Bid should not be revealed. If price change is envisaged due to any 

clarification, revised Bids in a separate sealed cover can be called 

from all the Bidders by ASI. 

ix. Terms and Conditions of Bidders 

1. Printed terms and conditions (General Conditions) of the Bidder will 

not be considered as forming part of their Bids. In case the proposal 

submitted has deviations from the requirements/specifications laid 

down in this RFP, the Bid shall be declared as unresponsive. No 

deviations / assumptions in any form mentioned elsewhere in the 

Bid, will be considered by ASI. 

x. Local Conditions 

1. It will be imperative on each Bidder to fully acquaint himself with the 

local conditions and factors at the respective locations, sites and 

offices which would have any effect on the performance of the 

contract and / or the cost. 

2. The Bidder is expected to obtain for himself on his own responsibility 

all information including permission from any local authority that 

may be necessary for preparing the bid and entering into contract. 

Otaiig suh ifoatio shall e at Biddes o ost. 

3. Failure to obtain the information necessary for preparing the bid 

and/or failure to perform activities that may be necessary for 

designing an optimal solution before entering into contract will in no 

way relieve the successful Bidder from performing any work in 

accordance with the contract entered into. 

4. It will be imperative for each Bidder to fully inform themselves of all 

legal conditions and factors which may have any effect on the 

execution of the contract as described in the bidding documents. 

5. It is the responsibility of the Bidder that such factors have properly 

been investigated and considered while submitting the bid proposals 



and that no claim whatsoever including those for financial 

adjustment to the contract awarded under the bidding documents 

will be entertained by ASI and that neither any change in the time 

schedule of the contract nor any financial adjustments arising 

thereof shall be permitted by ASI on account of failure of the Bidder 

to apprise themselves of local laws and conditions. 

xi. Last Date for Receipt of Bids 

xii. Late Bids 

1. Bids will be received by ASI at the address specified in section 6 of 

this RFP not later than the time and date specified. In the event of 

the specified date for the receipt of Bids being declared a holiday for 

ASI, the Bids will be received up to the appointed time on the next 

working day. 

2. ASI may, at its discretion, extend the last date for the receipt of bids 

by amending the RFP Document, in which case all rights and 

obligations of ASI and Bidders previously subject to the last date will 

thereafter be subject to the last date as extended. 

1. Any bid received by ASI after the last date for receipt of bids 

prescribed by ASI will be rejected and/or returned unopened to the 

Bidder. 

xiii. Modification and Withdrawal of Bids 

1. No bid may be altered / modified subsequent to the closing time and 

date for submission of bids. Unsolicited correspondences from 

Bidders will not be considered. 

2. No bid may be withdrawn in the interval between the last date for 

receipt of bids and the expiry of the bid validity period specified by 

the Bidder in the Bid. Withdrawal of a bid during this interval may 

esult i the Biddes fofeitue of their bid security. 

xiv. Address for Correspondence 

1. A“Is official mailing address, place and fax number is stated in 

Section 6 of this RFP. All correspondence shall be sent to ASI on 

this address only. 



xv. Contacting ASI 

c. Bid Submission Instructions 

1. No Bidder shall contact ASI on any matter relating to its bid, from 

the time of the bid opening to the time the Contract is awarded. 

2. A effot a Bidde to ifluee A“Is id ealuatio, id 

comparison or contract award decisions may result in the 

ejetio of the Biddes id. 

i. Procedure for Submission of Bids 

1. Prequalification Bid (1 hard copy and 1 duplicate copy) in one 

separate cover. 

2. Technical Bid (1 hard copy and 1 duplicate copy) in one separate 

cover. 

3. Commercial Bid (1 hard copy) in one separate cover 

4. Each of the Prequalification Bid, Technical Bid and Commercial Bid of 

the RFP should be covered in separate sealed covers super scribing 

Pe-Qualification Bid, "Tehial Bid" ad Coeial Bid 

respectively. Please Note that Prices should not be indicated in the 

Pre-Qualification Bid or Technical Bid and should only be indicated in 

the Commercial Bid. 

5. The Prequalification and Technical Bid should be duly initialed by 

Authoized “igato ad staped ith oet ae of the Biddes 

company/organization. 

6. The cover containing Prequalification Bid, Technical Bid and 

Commercial Bid as mentioned in clause above should be put in 

another single sealed envelope leal aked “eletio of 

Ipleetatio Age fo e-Ticketing Pojet. This eelope is to 

be superscribed with RFP Number, Due Date and the wordings DO 

NOT OPEN BEFORE 1500 hours on May 7 th . Same details are 



to be marked on the covers of the Prequalification, Technical Bids 

and Commercial Bid also. 

7. The cover thus prepared, encapsulating the three bids as mentioned 

above, should also indicate clearly the name, address and telephone 

number of the Bidder. 

8. The bids received after the due date and time shall be summarily 

ejeted ad etued to the Bidde delaig as Late suissio 

and the same shall not be opened. 

9. Each copy of the RFP should be a complete document and should be 

bound as a volume. The document should be page numbered and 

appropriately flagged and must contain the list of contents with page 

numbers. Different copies must be bound separately. If not properly 

bounded the ASI shall not be in any way responsible for loss of 

sheets due to inadvertent opening of the document at any stage and 

that affecting the prospects of the Bidder during the evaluation due 

to loss of these documents. 

10. As part of the bid, Bidder should also provide the pre-qualification 

and technical bid in editable soft copy format, in the form of a nonre-writeable 

CD–R (Compact Disc) as follows: 

One CD containing the pre-qualification bid - The CD containing 

pre-qualification should be sealed along with the hard copy of the 

Oigial op of the pe-qualification bid 

One CD containing the technical bid - The CD containing technical 

id should e sealed alog ith the had op of the Oigial 

copy of the technical bid. 

All CDs submitted by the Bidder must be in sealed covers. The 

sealed covers as well as the CD media must be duly signed by the 

Bidder usig a Peaet Pe/Make, should be super scribed 

ith Pe-Qualifiatio Bid / Tehial Bid / Coeial Bid 

(as the case may be) and should bear the name of the Bidder. 

Bidder must ensure that the information furnished by him in 

respective CDs is identical to that submitted by him in the original 

paper bid document. In case of any discrepancy observed by ASI 

in the contents of the CDs and original paper bid documents, the 



ii. Language of Bids 

information furnished on original paper bid document will prevail 

over the soft copy. 

Bidder must ensure that Technical Bid CD do not contain any 

Commercial items / prices. 

1. The Bids prepared by the Bidder and all correspondence and 

documents relating to the bids exchanged by the Bidder and ASI, 

shall be written in English language. 

iii. Documents Comprising the Bids 

1. The bid prepared by the Bidder shall comprise of the following 

components: 

A. Pre-Qualification Bid - The Prequalification shall comprise of the 

following: 

Annexure 1a of this volume - Cover Letter 

Annexure 1b of this volume – Prequalification Formats along with 

supporting documents 

Bid Security (Demand Draft/Bank Guarantee) 

RFP document fees (Demand Draft) 

Power of Attorney executed by the Bidder in favor of the Principal 

Officer or the duly Authorized Representative, certifying him/her 

as an authorized signatory for the purpose of this RFP 

B. Technical Bid - The Technical Bid shall comprise of the following: 

Annexure 1c of this Volume – Technical Formats 

Annexure 1c of this Volume – Technical Bid Letter 

C. Commercial Bid - The Commercial Bid shall comprise of the following: 

Annexure 1d of this volume - Commercial Bid Letter 

Annexure 1Di of this volume – Price Bid Format Breakdown of 

cost components 



iv. Format and Signing of Bid 

1. The Bidder shall prepare one copy of the Bid. 

2. The original and all copies of the bid shall be typed or written in 

idelile ik. All pages of the Oigial id douet shall e 

initialed and stamped by the person or persons signing the bid. 

3. The bid shall contain no interlineations, erasures or overwriting 

except as necessary to correct errors made by the Bidder, in which 

case such corrections shall be initialed by the person or persons 

signing the bid. 

4. The Bidder shall duly sign and seal its bid with the exact name of the 

firm/company to whom the contract is to be issued. 

5. The Bidder shall seal and mark the original and each copy of the Bid. 

6. If the outer cover of the bid is not sealed and marked as required by 

Annexure 1 of Volume 2, ASI will assume no responsibility for the 

bid's misplacement or premature opening. 

Clarification on RFP Document 

1. Bidder requiring any clarification on the RFP Document may submit 

his queries, in writing, at ASI's mailing address and as per schedule 

indicated in Annexure 2 of Volume 2. The queries must be 

submitted in spreadsheet format as provided in Annexure 3a of 

Volume 2. 

2. The Bidders shall bear in mind that their bids with any Technical or 

Commercial deviations will not be accepted. Thus, any issues / 

queries regarding Contract terms and conditions, Scope of Work, 

minimum requirements for Hardware infrastructure, essential 

features of the application / components and minimum staffing 

requirements etc., should be either clarified before bid submission or 

submitted to ASI in writing. 

3. ASI will respond in writing, to any request for clarification to queries 

on the RFP Document, received not later than the dates prescribed 

by ASI in Section 6 of this RFP document. Written copies of ASI's 

response (including the query but without identifying the source of 



inquiry) would be put up on the ASI website. Bidders are advised to 

keep browsing the information posted on the website. 

d. Bid Opening & Evaluation Process 

i. Opening of Bids by Purchaser 

1. ASI will open the Pre-Qualification and Technical Bids at the schedule 

given, in the presence of the representatives of the Bidders who 

choose to attend, at the time, date and place, as mentioned in Section 

6 of this document. 

2. The Bidders' names, modifications, bid withdrawals and the presence 

or absence of the requisite Bid Security and such other details as ASI, 

at its discretion, may consider appropriate will be announced at the 

bid opening. 

ii. Evaluation of Bids 

1. The selected Bidder must possess the requisite experience, strength 

and capabilities in providing the solution, equipment and services 

eessa to eet A“Is euieets, as desied i the ‘FP 

Document. The Bidder must possess the technical know-how and 

the financial wherewithal that would be required to successfully 

perform activities as per the Scope of Work in Section 1 of the RFP 

fo the etie peiod of the otat. The Biddes id ust e 

complete in all respect and covering the entire scope of work as 

stipulated in the RFP document. 

2. The evaluation process of the RFP proposed to be adopted by ASI is 

indicated under this Clause. The purpose of this Clause is only to 

provide the Bidders an idea of the evaluation process that ASI may 

adopt. 

3. Evaluation of the bids will be based on Lowest Commercial bid 

model. Commercial bids of those bidders who qualify through a 

technical evaluation shall be opened and successful bidders will be 

based on lowest commercial value. 

iii. Preliminary Examination 

1. ASI will examine the bids to determine whether they are complete, 

whether the bid format conforms to the RFP requirements, whether 

any computational errors have been made, whether required RFP 

fees and bid security has been furnished, whether the documents 



have been properly signed, and whether the bids are generally in 

order. 

2. ASI may waive any nonconformity or irregularity in a bid which does 

not constitute a material deviation according to ASI. 

iv. Clarification from the Bidder 

1. When deemed necessary, during the tendering process, ASI may seek 

clarifications on any aspect from any or all the Bidders. However, 

that would not entitle the Bidder to change or cause any change in 

the substance of the RFP submitted or price quoted. 

2. During the tendering process, the Bidders will make Technical 

presentations to ASI on experience, proposed project staff experience 

and proposed project approach and methodology. Purchaser expects 

that the Biddes Pogram Manager and other key personnel named in 

the proposal will take an active and leading role in these 

presentations. 

3. Bidders may also be required to demonstrate the features of the 

proposed products, if needed, or demonstrate proof of concept. 

I. Evaluation of Prequalification Bid 

1. In this part, the prequalification bid will be reviewed for determining 

the eligibility of the Bidder for the Project. 

2. This will be the first stage of the evaluation by ASI. 

3. Bidder needs to provide satisfactory documents against the Pre- 

Qualification criteria stated in RFP Volume 2 to clear the pre- 

qualification stage. 

II. Evaluation of Technical Bids 

1. In this part, the technical bid will be reviewed for determining the 

eligibility of the Bidder for the Project and to ascertain Compliance of 

the Technical bids with the RFP terms and conditions, technical 

requirements and scope of work as defined in this RFP. 

2. Only the technical bid of those bidders who qualify the prequalification 

criteria shall be evaluated. 



3. This shall be the second stage of the evaluation by ASI. Only those 

Bidders who cross the threshold level of Technical Evaluation 

idiated elo ad adhee to A“Is tehial euieets shall e 

considered for commercial evaluation. 

4. In case of no response by the Bidder to any of the requirements with 

regard to the contents of the Technical Bid, he shall not be assigned 

any marks for the same. 

5. Technical bid of the bidder shall be opened and evaluated for 

acceptability of Techno-functional requirements, deviations and 

technical suitability. Bidders shall respond to the requirements as 

explained in Volume 2 of RFP for their evaluation with regard to 

experience and qualification. Also, Bidder shall refer and respond to 

ALL technical requirements as mentioned in the RFP document. The 

evaluation process would also include a presentation of technical 

proposal by the Bidder. 

6. In order to qualify technically, a proposal must secure a minimum of 

70% of total marks after summing up. The Bidder would be 

technically evaluated out of 100 marks. Only those proposals which 

have a minimum score of 70 marks will be considered for opening of 

their Commercial Bid and evaluation thereof. 

7. Detailed technical evaluation criteria are provided in Annexure 1e of 

the Volume 2 of this RFP. 

III. Evaluation of Commercial Bids 

1. ASI will open the Commercial Bids of only Technically Qualified 

Bidders, in the presence of the representatives of the Bidder who 

choose to attend, at the time, date and place, as decided by ASI. 

2. The commercial bids shall be evaluated by ASI for completeness and 

accuracy. Arithmetical errors will be rectified on the following basis. 

If there is a discrepancy between the unit price and the total price 

that is obtained by multiplying the unit price and quantity, the unit 

price shall prevail and the total price shall be corrected. If there is a 

discrepancy between words and figures, the amount in words will 

prevail. 

3. The bid with the lowest commercial Cost (L1) will be the successful 

bidder. 



IV. Rejection Criteria 

1. Besides other conditions and terms highlighted in the RFP document, 

bids may be rejected under following circumstances: 

a. General Rejection Criteria 

Bids submitted without or improper Bid Security or tender fees 

Bids received through non-prescribed modes such as Fax/ e-Mail. 

Bids not bounded appropriately e.g. in the form of loose papers. 

Bids which do not confirm unconditional validity of the bid as 

prescribed in the RFP. 

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

/ misleading at any stage / time during the Tendering Process. 

Any effort on the part of a Bidder to influene A“Is id 

evaluation, bid comparison or contract award decisions. 

Bids received by ASI after the last date for receipt of bids 

prescribed by ASI, pursuant to Section 6. 

Bids without signature of duly authorized person(s) on all pages of 

bid documents 

Bids without power of authorization and any other document 

consisting of adequate proof of the ability of the signatory to bind 

the Bidder. 

b. Technical Rejection Criteria 

Technical Bid containing commercial details. 

Revelation of Prices in any form or in bids other than Commercial 

or by any reason before opening the Commercial Bid. 

Failure to furnish all information required by the RFP Document 

or submission of a bid not substantially responsive to the RFP 

Document in every respect. 

Bidders not responding to the complete scope of Work as 

indicated in the RFP documents, addendum (if any) and any 

subsequent information given to the Bidder. 

If the bid does not confirm to the timelines indicated in the bid. 

Non-Submission of list of Bill of Material (including quantities) in 

commercial proposal exactly same as the one in Technical 

proposal (without prices in technical proposal) 



c. Commercial Rejection Criteria 

Incomplete price bid 

Pie Bids that do ot ofo to the ‘FPs pie id foat. 

If there is an arithmetic discrepancy in the commercial bid 

calculations ASI shall rectify the same. If the Bidder does not 

accept the correction of the errors, its bid may be rejected. 

The commercial proposal should be in alignment with the 

technical proposal with regards to the BOM. Any deviation to the 

solution and change of solution components will lead to 

disqualification of that bid. 

The Bill of materials/ deliverables as given in the technical 

proposal should be in consonance with the commercial proposal. 

Any deviations between technical and commercial proposals in 

this respect shall make the proposal as being unresponsive and 

may lead to disqualification of the proposal. ASI reserves the right 

to take appropriate action in this regard. 



7. Award of Contract 

a. Post Qualification and Award Criteria 

i. ASI will determine to its satisfaction whether the Bidder selected as having 

submitted the best evaluated bid is qualified to satisfactorily perform the 

Contract. 

ii. This determination will take into account the Bidder's financial, technical, 

implementation and post-implementation strengths and capabilities. It will 

also include examination of the documentary evidence submitted by the 

Bidder as part of the bid and any other information as ASI deems necessary 

and appropriate. 

iii. An affirmative determination will be a prerequisite for award of the Contract 

to the Bidder. A negative determination will result in rejection of the 

Bidder's bid, in which event; ASI will proceed to the next lowest commercial 

bid to make a similar determination of that Bidder's capabilities to perform 

satisfactorily. 

iv. ASI is not bound to accept the best evaluated bid or any bid and reserves the 

right to accept any bid, wholly or in part. 

b. Purchaser's Right to Vary Scope of Contract 

i. ASI may at any time, by a written order given to the Bidder, make changes 

within the quantities, specifications, services or scope of the Contract as 

specified. 

ii. If any such change causes an increase or decrease in the cost of, or the time 

euied fo the Biddes pefoace of any part of the work under the 

Contract, whether changed or not changed by the order, an equitable 

adjustment shall be made in the Contract Price or time schedule, or both, 

and the Contract shall accordingly be amended. 

c. Purchaser's Right to Accept and Reject Bids 

i. ASI reserves the right to accept any bid, and to annul the RFP process and 

reject all bids at any time prior to award of Contract, without thereby 

incurring any liability to the affected Bidder or Bidders or any obligation to 

inform the affected Bidder or Bidders of the grounds for ASI's action. 

ii. ASI reserves the right to negotiate the commercials with the selected Bidder 

and seek revised commercial bid. 

d. Notification of Award 

i. Prior to the expiration of the period of bid validity, pursuant to Section 6 ASI 

will notify the successful Bidder in writing that its bid has been accepted. 

The Bidder shall provide his acceptance within 3 working days of such 

notification. 



ii. Upon the successful Bidder's furnishing of performance security pursuant to 

Section 6, ASI may notify each unsuccessful Bidder and will discharge their 

EMD, pursuant to Section 6 

e. Negotiations with the successful Bidder 

i. If required, negotiations will be held at the date, time and address intimated 

to the qualified and selected Bidder. Representatives conducting 

negotiations on behalf of the Bidder must have written authority to 

negotiate and conclude a Contract. 

f. Signing of Contract 

i. After completing negotiations ASI shall issue a Letter of Intent to the 

selected Bidder and promptly notify all other Bidders who have submitted 

proposals about the decision taken. 

ii. The Bidder will sign the contract within 15 working days of submission of 

Performance Bank Guarantee. 

g. Performance Security 

i. Within 15 working days of the receipt of notification of award from ASI, the 

successful Bidder shall furnish the performance security of 10% of total 

contract value in accordance with the Contractual & Legal Specification in 

the form of a Bank Guarantee. 

ii. Failure of the successful Bidder to comply with the requirement of Section 6 

shall constitute sufficient grounds for the annulment of the award and 

forfeiture of the bid security, in which event ASI may award the Contract to 

the next best evaluated bidder or call for new bids. 

iii. The Bank Guarantee shall be valid for 180 days more than the period of the 

contract. 



Annexure 1: Bid Formats 

a. Cover Letter 

Date: DD/MM/YYYY 

To 



Janpath, New Delhi – 110011 

Sir, 

[o the Biddes Lettehead] 

Subject: Selection of Implementation Agency for Ipleetatio of e-Ticketing 

Project, ASI 

Reference: RFP No: _____________________________ Dated _______________ 

With reference to your Request for Proposal fo “eletio of Ipleetatio 

Agency for Ipleetatio of e-Ticketing Project, ASI, we hereby submit our Pre- 

Qualification Proposal, Technical Proposal and Commercial Proposal for the same. 

We hereby declare that: 

a. We offer to supply equipment and provide services at the prices and rates 

mentioned in the attached commercial proposal 

b. We have not been banned or blacklisted by ASI or any Government department 

c. We have never been declared to be a willful defaulter by any Bank 

d. We or any person on our behalf will not engage in any corrupt, fraudulent or 

coercive practices to influence the Bidding Process. 

e. We hereby acknowledge and accept that ASI has the discretion to change or 

modify criteria as it deems appropriate while short listing of Agency for 

providing services. 



f. We have enclosed Demand Draft / Bank Guarantee of Rs. 50,00,000/- in favor of 

Dieto Geeal. , Ahaeologial “ue of Idia as Bid “euit, hih is alid 

for 180 days from the opening of the Technical Bid. 

g. We hereby declare that all information and details furnished by us in the 

Proposal are true and correct, and all documents accompanying such application 

are true copies of their respective originals. 

h. We agree to abide by our offer for a period of 180 days from the date of opening 

of technical bid prescribed by ASI and that we shall remain bound by a 

communication of acceptance within that time. 

i. We have carefully read and understood the terms and conditions of the RFP and 

the conditions of the contract applicable to the RFP. We do hereby undertake to 

provision as per these terms and conditions. 

j. In the event of acceptance of our bid, we do hereby undertake- 

1. To supply the products and commence services as stipulated in the schedule 

of delivery forming a part of the attached proposal. 

2. To undertake the project services for a period of 6 years from the date of 

signing of the contract. 

3. We affirm that the prices quoted are inclusive of delivery, commissioning, 

training, and providing facility management and inclusive of all out of 

pocket expenses, taxes, levies discounts etc. 

k. We do hereby undertake, that, until a formal contract is prepared and executed, 

this proposal, together with your written acceptance thereof and notification of 

award of contract, shall constitute a binding contract between us. 

l. We understand that the amount furnished by us as Bid security may be 

encashed under conditions enumerated in the RFP 

m. We understand that the ASI may cancel the bidding process at any time and that 

ASI is not bound to accept any bid that it may receive, without incurring any 

liability towards the bidder. 

In case of any clarifications please contact ___________________ email at 

________________________________________________________ 



Signature of Authorized Signatory (with official seal) 

Date ____________ 

Name ____________ 

Designation ____________ 

Address ____________ 

Telephone ____________ 

Fax ____________ 

E-mail address ____________ 



b. Pre-Qualification Letter 

To 




Sir, 

Subject: Selection of Implementation Agency for Ipleetatio of e-Ticketing 

Project, ASI 

Reference: RFP No: Dated 

We, the undersigned Bidder, having read and examined in detail all the RFP 

document in respect of Selection of Implementation Agency for “Ipleetatio 

of e-Ticketing Project, ASI do hereby propose to provide the services as specified in 

the RFP no. _______________________________ Dated ______________. 

We are hereby submitting our Pre-Qualification Bid (one original and two copies), 

which includes the following: 

Supporting Information for Pre-Qualification Conditions 

Bid Security of the prescribed amount and validity 

RFP document fees as prescribed 

Power of Attorney in favor of the authorized signatory 

We hereby declare that all the information and statements made in the Pre- 

Qualification related documents are true and accept that any misinterpretation 

contained in it may lead to our disqualification. 

We also agree to hold in trust any Confidential Information received by us as part of 

the tendering process, we shall maintain strict confidentiality in respect of such 



Confidential Information and in no event a degree of confidentiality less than we use 

to protect our own confidential and proprietary information. 

Yours sincerely, 

Bidder 

Authorised Signatory 

Name 

Designation: 

Company Seal 



c. Supporting Information for Pre-Qualification Conditions 

The Bidder is required to fill relevant information in each of the formats given below. 

The pre-qualification bid must contain documentary evidences and supporting 

information to enable Purchaser to evaluate the eligibility of the Bidder without 

ambiguity. 

S.No. Particulars 

Bidder Details 

1. Name of the company / firm 

2. Mailing address in India 

3. Telephone number 

4. Fax number 

5. E-mail address 

6. Name and designation of the 

authorized person 

7. Year of establishment and 

constitution of organization 

8. Whether the Firm / Company 

Pre-Qualification 

has any widely accepted 

certification. 

Evaluation Criteria 

Bidder Pre- 

Qualification 

Documentary Proof 

Required 

1. The Bidder should Certificate of 

Type of Documentary 

Evidence Provided 

Evidence 

Annexed at 

Page No. 


2. 

3. 

4. 


have been in 

operation in 

Information 

Technology in India 

for a period of at 

least 5 years as on 

31-03-12 

The Bidder should 

have annual turnover 

of minimum Rs. 100 

Crores or more in 

each of the last three 

financial year (ending 

31st March 2012) 

accruing from System 

Integration (including 

supply of hardware 

servers, components, 

devices etc.), 

development of IT 

applications 

Application 

Maintenance 

services. 

and 

The Bidder should be 

a profit making entity 

in last three financial 

years 

Bidder or the 

subcontracting firm 

should have atleast 

1000 full time 

Incorporation issued 

by the Registrar of 

Companies 

Duly certified 

statement from their 

appointed statutory 

auditor for the years 

2009-10, 2010 -11 

and 2011-12 

indicating the amount 

of turnover during 

these years 

Duly audited Financial 

statements from their 

appointed statutory 

auditor for the years 

2009-10, 2010-11 and 

2011-12 indicating 

profit during these 

years 

Certificate by the 

Statutory Auditor or 

Company Secretary of 

the firm 

Year Bidder’s 

turn 

over 

2011 – 12 

2010 – 11 

2009 – 10 


5. 


professionals on its 

rolls out or with 

Subcontracting firm; 

of which 250 should 

be managerial 

resources. 

The Bidder should 

have successfully 

completed 

implementation of at 

least one (1) 

assignment in e- 

ticketing/ e 

commerce solutions 

in a Government 

Department/ Client 

in India or (2) 

assignments similar 

in nature in the last 3 

years 

6. Bidder should have 

experience of 

implementing at 

least one (1) similar 

project in a multi- 

location scenario 

(atleast 10) in India 

worth atleast Rs. 5 

crores covering 

ticket / bill printing 

& device-based 

Purchase Order / 

Work Order and 

Completion 

certificate/ client 

letter/ client e-mail/ 

reference to the 

contract/ RFP/ 

website from client. 

Similar assignment: 

shall mean a project 

that involves 

implementation of 

web based purchase 

services and billing at 

the counter using a 

centralized POS 

Application 


7. 

8. 

9. 


10. 

validation 

same 

of the 

Bidder should have 

certification of 

ISO 9001:20000 Or 

CMMi Level 3 or 

above 

Bidder should submit 

RFP fees of Rs 10,000 

(Rupees Ten 

Thousand) in form of 

Demand Draft (DD) 

Bidder should submit 

Earnest Money 

Deposit (EMD) of Rs 

50,00,000 (Rupees 

Fifty Lakh only) in the 

form of a Demand 

Draft (DD) or Bank 

Guarantee 

Power of Attorney 

authorizing the 

Copy of valid 

certificate issued to 

the Delivery Center of 

the Bidding 

Organization by 

respective agencies. 

Note: Organizations 

that are being 

currently assessed for 

the requisite 

certification level shall 

not be considered. 

Only the centers that 

have got certified 

shall be eligible for 

bidding. 

Demand Draft drawn 

i fao of Director 

General, 

Archaeological Survey 

of Idia fo a 

Scheduled Bank 

payable at New Delhi. 

Demand Draft/ Bank 

Guarantee drawn in 

fao of Dieto 

General, 

Archaeological Survey 

of Idia fo a 

Scheduled Bank 

payable at New Delhi. 

Power of Attorney and 

a certified true copy 

of all agreements 

DD Number: 

DD Date: 

Issuing Authority / 

Bank: 

DD Number: 

DD Date: 

Issuing Authority / 

Bank: 



Bidder in favor of the 

Principal Officer or 

the duly Authorized 

Representative to 

sign/ execute the 

proposal as a binding 

document and also 

execute all relevant 

agreements forming 

part of RFP/ bid 

process should be 

attached 

revealing the 

respective roles and 

responsibilities in 

meeting the overall 

scope of 

requirements of the 

Project. 

Prospective subcontractor Statement 

Bidder shall identify all prospective subcontractors, if any, which the bidder will 

engage, to provide the services required under this RFP. The bidder shall not subcontract 

the work relating to the customization and design of the e-Ticketing 

Solution (ETS) application and application deployment at DC and DRC. For each 

proposed subcontractor, bidder shall provide the following: 

o Brief description of nature of products/services to be provided by 

subcontractor; 

o Head and branch offices (if responsible for work under this contract) (provide 

street and mailing addresses, phone, fax and email); 

o Date, form and state of incorporation; 

o Contract administrator (Name, business address, fax, phone and email 

address of individual responsible for administering any contract that might 

result from this RFP); 

o Company principals (Name, title and business address); and, 

o Current or prior successful partnerships with proposed subcontractor 

including client reference (Contact Name, Phone Number, dates when 

services were performed). 

Bidder 

Authorized Signatory 

Name 

Designation: 

Company Seal 



d. Technical Bid Formats 

To 

i. Technical Bid Letter 




Sir, 

Subject: Selection of Implementation Agency for Ipleetatio of e tiketig 

Project 

Reference: RFP No: _____________________________ Dated ______________ 

Sir, 

We, the undersigned Bidder, having read and examined in detail the entire RFP 

document in respect of Selection of Implementation Agency for Ipleetatio of 

e ticketing Project, do hereby propose to provide the services as specified in the 

RFP No. _____________________________ Dated ______________. 

We declare that all the services shall be performed strictly in accordance with the 

RFP documents and hereby agree for unconditional acceptance of all the terms and 

conditions set out in the bid document. 

We confirm having submitted the information as required by you as Prequalification 

Criteria. In case you require any other further information/documentary proof in 

this regard before evaluation of our bid, we agree to furnish the same in time to your 

satisfaction. 

We hereby declare that our bid is made in good faith, without collusion or fraud and 

the information contained in the bid is true and correct to the best of our knowledge 

and belief. 



We understand that our bid is binding on us and that you are not bound to accept 

bid you receive. 

Thanking you. 

Yours faithfully 

Bidder 

Authorized Signatory 

Name 

Designation 

Company Seal 



ii. Credential Format 

Credentials for each of the pre-qualification conditions should be furnished in the following 

format: 

S. No. Items Details 

General Information 

1. Customer Name 

2. 

Project Details 

Name of the contact person and 

contact details for the client of the 

assignment 

3. Project Title 

4. Start Date / End Date 

5. Date of Go-Live 

6. Total Cost of the project 

7. 

8. 

Current Status (Live / completed / 

on-going / terminated / 

suspended) 

Please indicate the current or the 

latest AMC period with the client 

(From Month –Year to Month- 

Year) 

9. No. of Locations 

10. Man-month effort involved 

11. 

12. 

Type of Project: e-commerce 

Portal/ e-ticketing / other relevant 

applications 

Size of the project 

Solution architecture employed 

and core components 



13. 

Number of total users and 

concurrent users of the solution at 

the client location(s): 

Enclosures Required 

Enclosure A: 

Total users 

Concurrent users, 

this should correlate 

to actual users of the 

solution. Not portal 

visitors 

Brief narrative Description of the Project and the services rendered by your company (not 

more than one page) 

Enclosure B: 

Please provide copies of Work Order or Certificate of Completion for Complete Projects from 

Authorized officials in the Government Departments/ Client 

iii. Overview of Proposed Solution 

Please poide eleat details o “olutios & “eies speifi to Biddes proposal 

under below mentioned Headings. The list is indicative and can be populated with 

other relevant headings. 

BIDDERS ARE ADVISED TO REFRAIN FROM ATTACHING PRODUCT BROCHURES AND 

CATALOGUES 

(Bidders are liable to get dis-qualified if non adherence to the above) 

Capabilities of the proposed solution to address the functional requirements 

a. Identification of Application Software 

b. Technologies proposed 

c. Solution Architecture 

d. Performance solution Scalability and High Availability solution 

e. Deployment Architecture 

f. Server Hardware Technologies 

g. DC and DR solution 

h. Network Plan at DC and DR 



i. Security Architecture 

j. Testing Plan and Phasing 

k. Testing Tools proposed 

l. Approach for Quality Management 

m. Service Approach for Facility Management Service, Technical Support 

n. Manpower Details 

o. Compliance matrix to the Functional & Technical Requirement 

p. Bill Of Material (unpriced) 

iv. Manpower details 

Note: For the Key Personnel (refer Section 3.3 Volume 2 of this RFP), please provide 

profile in the following format: Profile of Personnel 

Note: Please note that CV should not be more than 2 pages 

 

1. Specify Proposed 

position / role to be 

played in the project 

(whether prime or 

alternate) 

2 Current Designation/ 

Job title 

No. of years with 

current organization 

3 Date of Birth 

4 Nationality 

5 Educational 

Background 

including 

Training/Certification 

including 



 

institutions, % of 

marks, specialization 

areas 

6 Employment Record (Starting with present position, provide details regarding name 

of organizations worked for, Designation, Responsibilities, tenure 

etc. in reverse order) 

7 Relevant Experience (Give an outline on the experience most pertinent to tasks 

mentioned in the project. Describe degree of responsibility held 

on these relevant assignments – Up to half of a page). 

8 Certification I, the undersigned, certify that to the best of my knowledge and 

belief, this CV correctly describes me, my qualifications and my 

experience and proposed staff member is the permanent 

employee of our organisation. I understand that any willful 

misstatement described herein may lead to disqualification or 

dismissal, if engaged. 

Date: 

Place Signature of the Candidate 

Signature of Authorized Signatory 

Date: 

Company Seal 



e. Commercial Bid Letter 

To 

The 




Sir, 

Subject: Selection of Implementation Agency for Ipleetatio of e tiketig 

Project 

Reference: RFP No: __________________________ Dated _______________ 

Sir, 

We, the undersigned Bidder, having read and examined in detail the entire RFP 

document in respect of Selection of Implementation Agency for Ipleetatio of 

e ticketing Project, do hereby propose to provide the services as specified in the 

RFP No. ______________________ Dated _________________. 

We undertake, if our proposal is accepted, to adhere to the implementation plan 

(Project Schedule) for implementing the e ticketing solution, operations and 

maintenance of the system. 

We agree for unconditional acceptance of all the terms and conditions in the bid 

document. 

All the prices mentioned in our RFP are in accordance with the terms as specified in 

the RFP documents. All the prices and other terms and conditions of this RFP are 

valid for a period of 180 calendar days from the date of opening of the technical bids. 

We have studied the relevant clause(s) in Indian Tax Laws and hereby declare that if 

any taxes, surcharge, Professional and any other corporate Tax in altercated under 

the laws, we shall pay the same. 



We have indicated in the relevant schedules enclosed, the unit rates for the purpose 

of on account of payment as well as for price adjustment in case of any increase to / 

decrease from the scope of work under the contract. 

We further confirm that the prices stated in our bid are in accordance with RFP. 

We confirm having submitted the information as required by you in your Instruction 

to Bidders. In case you require any other further information/documentary proof in 

this regard before evaluation of our bid, we agree to furnish the same in time to your 

satisfaction. 

We declare that our bid prices are for the entire scope of the work as specified in the 

Scope of Work and bid documents. These prices are attached with our bid as part of 

the bid. 

We hereby declare that in case the contract is awarded to us, we shall submit the 

Performance Bank Guarantee within 15 working days of award notification. 

We hereby declare that our bid is made in good faith, without collusion or fraud and 

the information contained in the bid is true and correct to the best of our knowledge 

and belief. 

We understand that our bid is binding on us DURING THE VALIDITY PERIOD OR THE 

EXTENSIONS THEREOF and that you are not bound to accept a Bid you receive. 

We confirm that no deviations are attached here with this commercial offer. 

Thanking you, 

Yours faithfully, 

(Signature of the Bidder) 

Printed Name 

Designation 

Seal: 

Date: 

Place: 

Business Address: 



i. Price Bid format - Breakdown of Cost Components 

Form A: Detailed Pricing Sheet 

S. No Description Total 

A. Pricing Summary for capital expenditure (Capex) 

(Form 1, Item 7) 

B. Operational Expenditure (Opex) during the first 

year (Form2) 

C. Operational Expenditure (Opex) during the 

second year (Form2) 

D. Operational Expenditure (Opex) during the third 

year (Form2) 

E. Operational Expenditure (Opex) during the fourth 

year (Form2) 

F. Operational Expenditure (Opex) during the fifth 

year (Form2) 

G. Total (A to H) 

Price 

(INR) 


Taxes and 

Other 

Duties 

(INR) 

Total Amount 

(INR) 

(Exclusive of 

Taxes) 

Total 

Amount in 

Words


Form 1: Pricing Summary for Capital Expenditure (Capex) 

S. No 

Description 

Services provided during Implementation Phase 

1. 

2. 

3. 

4. 

Cost of ASI e-Ticketing System (ETS) Application Software 

(Total from Form 1.1.1) 

Cost of e Ticketing Implementation and Rollout including 

Integration & Testing (Total from Form 1.1.2) 

IT infrastructure and site preparation at Monument sites 

(Total from Form 1.2) 

IT infrastructure at DC & DRC (Total from Form 1.3) 

5. Any other items 

6. Total Cost 

Total Price 

(INR) 


Taxes and 

Other Duties 

(INR) 

Total amount 

(INR) 

Total 

amount 

In 

words


Form 2: Operational Expenditure (Opex) (Prepare one form per year) 

S. 

No 

Description No. of 

Warranty, AMC & Operations Support 

1. 1 

for IT infrastructure at DC and DRC 

2. 

Warranty, AMC & Operations Support 

for IT and Non-IT infrastructure at Point 

of Sale (monument sites) 

Manpower Deployment at monument 

3. 4 sites (includes ticket issuers and 

verifiers) as defined in the Annexure-3, 

Vol-1 

4. 5 in RFP Vol. 1 (includes Support 

5. 

Technical Helpdesk Support as defined 

Managers and Support Executives) 

Post Implementation Support (includes 

Onsite Operations Manager) 

Man- 

power 

Total Cost (INR) Taxes & Other 


984 

Duties (INR) 

Total Amount 

(INR) 

Total Amount in 

words


S. 

No 

Description No. of 

Annual Technical Support (ATS) for all 

6. 6 

licensed Software 

7. 

8. 

Consumables (Ticket stationary, 

Ribbons, UPS Batteries etc.) 

DC-DR Hosting charges (for shared 

services) 

9. 8 Any other Maintenance Services 

10. 9Total cost (n th year) 

Man- 

power 

Form 1.1.1: Cost for e-Ticketing System (ETS) Application Software 

S. 

No. 

Application 

Software 

Cost per Unit 

(INR) (A) 

No. of 

licenses (B) 

Total Cost (INR) Taxes & Other 

Customization 

Cost (INR) (C ) 


Duties (INR) 

Taxes 

(INR) (D) 

Total Amount 

(INR) 

Total 

Amount 

(INR) 


words 


words


1. 

2. 

3. 

Web based Online 

Ticketing application 

E-Ticketing 

application for Point 

Of Sale terminals 

E-Ticketing 

application for 

handheld ticket 

dispensing device 

along with Software 

Development Kit 

(SDK) 

Form 1.1.2: Cost of e Ticketing Implementation and Rollout including Integration & Testing 

Item 

Description 

Unit of 

Measurement 

Price 


per 

Unit 

Number 

of Units 

Total 

Price 

Total Cost 

Taxes & 

Other Duties Total Amount in INR


Specify the key 

personnel skill (as per 

RFP) 

Add new row per skill 

set (e.g. Program 

Manager, Business 

Analyst, Manager 

Infrastructure, Solution 

Architect Application 

and Database 

Administrator) 

Total Amount in INR N/A N/A N/A N/A 

Total Amount in words 



Form 1.2: IT infra & Site preparation at Monument sites 

S. No. Description Cost 

1 Monuments 

per 

Unit 

(INR) 

No of 

Units 

a. EDesktop 

for POS 179 

. 

b. Handheld Ticket 

dispensing device 

Total 

Price 

(INR) 

Taxes and other duties 

(INR) 


131 

c. Ticket Printers 85 

d. Network switch(No. of 

monuments) 

e. Bar Code Reader/ 

Scanners 

f. UPS (No. of 

monuments) 

g. LAN cabling work (No. 

of monuments) 

41 

186 

68 

68 

Total amount 

(INR) 

Total amount in words



per 

Unit 

(INR) 

No of 

Units 

h. Currency Chest 116 

i. Currency Counting 

machine 

j. Fake currency detection 

machine 

k. Drop box (for 

Feedback) 

l. Operating system for 

desktop machines 

m. Operating system for 

handheld ticket 

dispenser 

Total 

Price 

(INR) 


(INR) 


29 

29 

116 

179 

131 

Total amount 

(INR) 




per 

Unit 

(INR) 

No of 

Units 

n. Antivirus Software 179 

o. Any other 

infrastructure (please 

specify complete list) 

p. Total Cost ] 

Total 

Price 

(INR) 


(INR) 


Total amount 

Note: The above is just an indication of the requirement which might vary depending on the site survey done by the IA 

(INR) 



Form 1.3: IT infrastructure at DC and DRC including necessary hardware, software and other components. 

S.No. Item Description No. Of 

1. Data Centre Components 

Servers 

Web Server 


Application Server 


Any other server, 

please mention 

Software 



Units 


Unit 

Rate 

Quote amount 

(INR) 

Taxes and other 

duties 

Total Amount 

(INR) 

Amount in words



SLA Measurement 

Tools 

Any other software, 


Bandwidth for DC 

WAN connectivity for 

internet gateway (10 

Mbps) 

Replication links 

between DC & DR (2 

Mbps) 

Other(s) - please 

specify 

Units 

2. Disaster Recovery Centre Components 


Unit 

Rate 

Quote amount 

(INR) 


duties 

Total Amount 

(INR) 

Amount in words



Servers 

Web Server 


Application Server 


Any other server, 


Software 



Units 


Unit 

Rate 

Quote amount 

(INR) 


duties 

Total Amount 

(INR) 

Amount in words



Enterprise Antivirus 

System 

SLA Measurement 

Tools 

Any other software, 


Bandwidth for DR 

WAN connectivity for 

internet gateway (10 

Mbps) 

Replication links 

between DC & DR (2 

Mbps) 

Units 


Unit 

Rate 

Quote amount 

(INR) 


duties 

Total Amount 

(INR) 

Amount in words



Other(s) - please 

specify 

Grand Totals 

Form 1.4: Blended person month rates 

Units 


Unit 

Rate 

Quote amount 

(INR) 


duties 

Total Amount 

(INR) 

Amount in words 

The bidder is expected to quote incremental costs on account of out-of-scope activities that shall be covered under Change request mechanism. 

The per person month cost quoted shall not be considered for the purpose of commercial evaluation. 

(All Prices in Indian Rupees) 

Note: 

IA is required to make his own Bill of Material Assessment. An indicative list of specifications is provided in RFP volume 1. IA is 

required to provide an undertaking for the Bill of Materials along with the Bid. 

IA should provide all prices, quantities as per the prescribed format under this Section. IA should not leave any field blank. In 

ase the field is ot appliale, “I ust idiate 0 )eo i all suh fields. 

The IA is required to provide license quotes considering below mentioned numbers. In case additional licenses are required 

during the implementation stage, IA will also provide per user license rates and the applicable discount on each license due to 

bulk purchase. 

It is mandatory to provide breakup of all Taxes, Duties and Levies wherever applicable and/or payable.


ASI may, at its discretion, decide to procure items mentioned in the Bill of Materials directly. 

ASI reserves the right to ask the IA to submit proof of payment against any of the taxes, duties, levies indicated. 

ASI shall take into account only the Grant Total which is exclusive of all Taxes, Duties & Levies for the purpose of Evaluation. 



f. Evaluation of Technical Bids 

The evaluation of the technical bids will be based on the following parameters: 

Measurement Method 

Technical Evaluation 

Parameter 

Understanding of RFP 

Understanding of RFP 

and compliance to 

the Functional 

Requirements 

The bidder is 

expected to propose 

a solution that covers 

all aspects of the 

functional 

requirements and 

shall clearly articulate 

how the solution 

complies with all the 

requirements 

mentioned in the FRS 

and RFP. 

Proposed 

Architecture & 

Solution 

Relevant Past 

experience 

Technologies 

Proposed 

The bidder shall prepare a compliance checklist for all the 

Functional Requirements under E-Ticketing System. Full 

Compliance to be awarded full marks and partial 

compliance, marks to be awarded on pro rata basis 

1. Mapping of functionality to the proposed 

application 

2. Past solution experience relevance to proposed 

application, including aspects like: 

a. Project providing e-services, with 

transaction volumes of over 3 Lakh per 

annum 

b. E-Service Delivery with a multi layer 

architecture comprising portal solutions for 

providing eServices to users including 

online payment facilities 

c. Geographically dispersed rollout and multi 

location operation 

d. Providing managed services compliant with 

ITIL/ITSM standards 

Reasoning for choosing a particular technology stack, 

middleware stack, design principles based on chosen 


Qualifying 

Marks 

10 

35



Parameter 


parameters (e.g. ease of usability, superior performance, 

cost optimization, conformance to industry standards 

(prescribed in the RFP or otherwise), ease of maintenance 

etc.). 

Payment Solution Solution proposed for different types of payment, 

payment gateways, payment accounting plan 

Performance Solution Behaks fo pefoae ith espet to “LAs, 

solution proposed for measurement 

Scalability and High 

Availability Solution 

Proposed POS 

Solution for Ticketed 

Monuments 

Deployment 

Architecture at DC 

and DR 

Bill of Material for the 

complete proposed 

solution (without 

price) 

Plan and provision for scalability, high availability and 

tools proposed. 

Proposed Point of Sale Solution for the ticketed 

monuments. 

Infrastructure components and Deployment 

Architecture, 

Complete Un-priced BOM to be specified 

DC and DR Solution Plan including proposed Components and Services in DC & 

DR including BCP Plan and DR strategy and Plan 

Network Plan at DC 

and DR 

Plan for networking and connectivity between DC and DR 

– Replication links and internet gateway bandwidth 

Security Architecture Methodologies and technologies for securing 

a. The application 

b. Hardware Infrastructure 

c. Network 

d. Threats Monitoring 


Qualifying 

Marks



Parameter 

Testing Plan and 

Phasing 

Testing Tools 

Proposed 

Quality Assurance 

Approach and Project 

risk management 

Implementation and 

Operations & 

maintenance 

Implementation 

Strategy 

Project Timelines and 

Plan 


approach 

Number of key people 

proposed. 

Note: The number of 

people committed for 

the proposed 

duration shall be 

maintained at any 

cost. Key resources 

like Program 

Manager, Manager 

Infrastructure, 

Business Analyst, 

Database 

Administrator and 

Solution Architect etc. 

shall be proposed in 

the bid. These 


Plan for phasing the testing, methodologies for creating 

test plans and test cases, types of testing etc. 

Tools proposed for testing covering all relevant types of 

testing 

Plan for quality assurance, Project risk management 

including risk assessment, risk monitoring, mitigation 

strategy & plan 

1. IT Services management Helpdesk Solution 

2. DC/DRC operation 

3. POS operation 

4. Proposed manpower deployment at ticketed 

monuments and Grievance management solution 

Propose an implementation strategy that complements 

the Project Plan envisaged in the RFP 

Strategy 

Propose a master project timeline that complies with the 

overall timelines of the project 

Propose a Project Management approach for the project 

and project management tools 

Indicate the number of people proposed for the project in 

key levels of expertise, namely, Program Managers, 

Manager Infrastructure, Business Analyst, Database 

Administrator, Solution Architect, Business Analysts and 

Operations Team etc. 


Qualifying 

Marks 

45



Parameter 

resources shall be 

responsible for 

managing the project 

and shall not be 

replaced except if 

they leave 

the rolls of the 

iddes ogaizatio. 

These 

same resources shall 

be responsible for 

“Presentation” 

Experience of key 

personnel 

Relevant skills of key 

personnel. 

Qualifications of 

proposed personnel 

Certifications of 

proposed manpower. 


The total experience of PMs and Architects (software and 

hardware) shall be clearly articulated. High level of 

expertise in Program/Delivery Manager and Solution 

Architects (more than 8 years) is desirable. The same team 

shall be committed to the project. 

The Architects should have architected complex solutions. 

All manpower (excluding support staff) proposed should have a 

Bachelor’s / Master’s degree in Technology / Engineering or 

MCA 

The proposed manpower shall be certified in 

various areas of expertise 


Qualifying 

Marks 

Presentation 10 

Presentation / Proof 

of Concept 

1. Clear understanding of the business functions 

2. Proposed Solution and technology 

3. Previous Project Experience 

4. Proposed Project Team 

5. Implementation Strategy 

6. Operations & Maintenance 

Total Marks 100


Annexure 2: Request for Clarification Format 

Sr. 

No. 

a. Format for clarifications 

Bidder requiring any clarification on the RFP Document may submit his queries, in 

writing, at the ASI's mailing address and as per schedule indicated in Section 8.1.2. The 

queries must be submitted in Microsoft Excel format as follows: 

Volume No. Section No. & Page 

No. 

b. Clarification on RFP Document 

Clause in RFP Clarification Sought 

i. The Bidders shall bear in mind that their bids with any Technical or Commercial 

deviations will not be accepted, Thus, any issues / queries regarding Contract terms 

and conditions, Scope of Work, minimum requirements for Hardware 

infrastructure, essential features of the application / components and minimum 

staffing requirements etc., should be either clarified before bid submission or 

submitted to the ASI in writing. 

ii. The ASI will respond in writing, to any request for clarification to queries on the RFP 

Document, received not later than the dates prescribed by ASI. Written copies of 

the ASI's response (including the query but without identifying the source of 

inquiry) would be put up on the www.asi.nic.in website. Bidders are advised to keep 

browsing the information posted on the website. 



Annexure 3: Bid Security Format 

1. I osideatio of ________________ heeiafte alled the ASI epeseted 

________________, on the first part and M/s ____________ of ___________ 

heeiafte efeed to as Bidde o the “eod pat, haig ageed to aept the 

Earnest Money Deposit of Rs. 50,00,000.00 (Rupees Fifty Lakhs Only) in the form of Bank 

Guarantee for the Request for Proposal for procurement of _________ we __________ 

Nae of the Bak, heeiafte efeed to as the Bak, do hereby undertake to pay 

ASI forthwith on demand without any demur and without seeking any reasons 

whatsoever, an amount not exceeding Rs. 50,00,000.00 (Rupees Fifty Lakhs Only) and 

the guarantee will remain valid up to a period of 180 days from the due date of the 

tender. It will, however, be open to ASI to return the Guarantee earlier than this period 

to the bidder, in case the bidder has been notified by ASI as being unsuccessful. 

2. In the event of the bidder withdrawing the tender before the completion of the stages 

prior to the Commercial negotiations or during the Commercial negotiations, as the case 

may be, the EMD / Bid Security deposited by the bidder stands forfeited to the 

Government. We also undertake not to revoke this guarantee during this period except 

with the previous consent of the Government in writing and we further agree that our 

liability under the EMD / Bid Security shall not be discharged by any variation in the 

term of the said tender and we shall be deemed to have agreed to any such variation. 

3. No interest shall be payable by ASI to the bidder on the guarantee for the period of its 

currency. 

4. Notwithstanding anything contained hereinabove: 

a) Our liability under this Bank Guarantee shall not exceed and is restricted to Rs. 

50,00,000.00 (Rupees Fifty Lakhs only) 

b) This Guarantee shall remain in force up to and including _________ . 

c) Unless the demand/claim under this guarantee is served upon us in writing 

before_________ all the rights of ASI under this guarantee shall stand automatically 

forfeited and we shall be relieved and discharged from all liabilities mentioned 

hereinabove. Dated this ___________day of ____________________ 2013 

(Agent/Manager) 

For the Bank of _______________ 


Request For Proposal for 

e-Ticketing Project 

For Archaeological Survey of India, Volume-III 

Master Service Agreement and Service Level Agreement 

April 2013

RFP for e-Ticketing Project Volume-III 


1. INTRODUCTION .........................................................................................................4 

2. ROLES & RESPONSIBILITIES .........................................................................................5 

3. PROGRAM GOVERNANCE STRUCTURE ........................................................................6 

4. SERVICE LEVEL AGREEMENTS .....................................................................................7 

5. DRAFT MASTER SERVICES AGREEMENT ......................................................................9 

6. SCHEDULE I .............................................................................................................. 52 

6.1. PURPOSE ..................................................................................................... 52 

6.2. CHANGE CONTROL NOTE ("CCN") ................................................................. 52 

6.3. QUOTATION ................................................................................................ 53 

6.4. COSTS .......................................................................................................... 54 

6.5. REPORTING .................................................................................................. 54 

6.6. OBLIGATIONS .............................................................................................. 54 

7. SCHEDULE II ............................................................................................................. 55 

8. SCHEDULE III ............................................................................................................ 61 

9. SCHEDULE IV ............................................................................................................ 64 

10. SCHEDULE V ............................................................................................................. 67 

11. SCHEDULE VI ............................................................................................................ 68 

12. SCHEDULE VII ................................................................................................................. 72 

13. SCHEDULE VIII .......................................................................................................... 76 

14. SCHEDULE IX ............................................................................................................ 88 







HLD High Level Design 


IEEE Institute of Electrical and Electronics Engineers 


LLD Low Level Design 


NOC No Objection Certificate 

PKI Public Key Infrastructure 




SPOC Single Point of Contact 






1. Introduction 

ASI proposes an e-Ticketing initiative to harness the power of ICT Platform for its vision 

”To esure trasparet, eas, efficiet ticketig sste usig ICT to facilitate world class 

Visitor eperiece” 

In order to streamline its processes and increase efficiency and effectiveness of services, ASI 

has undertaken a comprehensive exercise to implement ICT based e-Ticketing system across 

all the protected/Ticketed monuments across India. The ICT based system is also aimed to 

bring in transparency and sustainability of the processes. 

ASI intends to establish a state of the art e-Ticketing solution which envisions the capability 

of the solutio to sell ad ook tikets olie ad at the Poit of “alePO“ outes fo all 

the ticketed monuments using a centralized solution. The system should be hosted on a 

robust server which is capable of dealing on real time basis. The system should be able to 

generate tickets and validate the entry to the monuments. 

As part of the tender process, ASI is releasing this RFP to receive responses from eligible 

bidders, to evaluate the bids and select the most appropriate Implementing Agency (IA). 

This RFP has been prepared to invite bidders to submit their proposals to implement and 

maintain e-Ticketing system for ASI. Information used for the preparation of this RFP has 

been made available from relevant and published sources of information. Nonetheless, 

bidders are required to make informed evaluation and decision based on their judgment. 





Volume I: Functional, Technical and Operational Requirements 

Volume I of RFP brings out all the details of solution requirements of the e-Ticketing 

system. This volume also gives the details of the other requirements (functional, 

operational and technical) of the e-Ticketing project. 

Volume II: Instruction to Bidders and Bidding Terms and Conditions 

Volume II of RFP brings out details of the bidding process, bidding terms and conditions 

and all that may be needed by the bidders to understand bidding process. 

Volume III: Master Service Agreement and Service Level Agreement 

Volume III of RFP explains the contractual terms that will govern the project 

implementation and operation. This includes the draft Master Service Agreement and 



Service Level Agreement that ASI intends to sign with the successful bidder or the selected 

Implementing Agency. 

This Document is Volume III. 

2. Roles & Responsibilities 

2.1. Role of ASI 

ASI is the owner of the Project; in that role, ASI is expected to discharge the following 

responsibilities: 

Lay down the metrics for the success of the Project; 

Own the core and critical assets of the Project; 

Approve the budget and release funds required for the Project; 

Facilitate and/or approve the deputation of employees of the GoI to the e-Ticketing 

Project; 

Constitute a Program Steering committee and Program Operations Committee 

Constitute a Program Management Unit (PMU) for facilitating smooth 

implementation of e-Ticketing Project; 

Review the performance of the Implementation Agency through PMU; 

Issue directions to the PMU and IA as may be needed; 

Ensure that all the offices under ASI take active part in the project; 

Identify & nominate competent personnel from ASI and project locations to 

participate in the Acceptance Testing; 

Engage a third party for acceptance testing and audit of security & controls of the 

application & infrastructure established for e-Ticketing system; 

Facilitate the training programs that will be conducted by the IA. 

Facilitate Change Management efforts by Issuing circulars, instructions, etc., to effect 

changes to existing roles and responsibilities of employees, adoption of 

reengineered processes in participating divisions and such other matters as may be 

necessary from time to time; 

Facilitate the communication program that will be conducted by the IA for 

popularizing the new e-Ticketing system. 

Periodically review and test SLA Monitoring System implemented by IA for accuracy 

and completeness in the reports generated from the system. 

2.2. Role of Implementation Agency 

The responsibilities of IA are as specified in the Statement of Work of volume I of this 

RFP. 



3. Program Governance Structure 

3.1. Program Governance Approach 

The objectives of the Program Management activity are: 

Monitor the Project plan to ensure that all the activities have commenced and 

completed as per the phase-wise plan drawn by IA. 

Report the project progress to the Operations Committee of ASI as per agreed 

frequency. 

Identify risks and facilitate IA in developing mitigation strategies and implementing 

them 

The proposed Program Governance Structure has been detailed in Section 10 of Volume I of 

this RFP. Program Management Unit (PMU) to be set-up by ASI will play a key role in the 

exercise of Program Management activities. 

3.2. Implementation Agency’s Program Management structure requirement 

IA is required to establish a well-defined and properly staffed Program Management (PM) 

team structure in place for ensuring a smooth implementation of the Project. The focus 

should be to have the right mix of personnel in the PM team with respect to both the area 

of expertise as well as the relevant experience in that area. It may be noted that the PMUs 

to be established by ASI, as detailed in sections 2.1 & 3.1 above, should not be construed as 

a substitute for the responsibility of the IA to establish a full-fledged PM team at its own 

initiative and cost. 



4. Service Level Agreements 

Following section outlines the key service level requirements for ASI system, which needs to be 

ensured by the IA during the operations and maintenance period. These performance 

requirements shall be strictly imposed and a third party audit/certification agency shall be 

deployed for certifying the performance of the IA against the target performance metrics as 

outlined in this volume of the RFP. Certification shall be done by a third party audit agency 

appointed by ASI. The SLA monitoring shall be performed/reviewed on a quarterly basis. During 

the Contract period, it is envisaged that there could be changes to the SLA, in terms of addition, 

alteration or deletion of certain parameters, based on mutual consent of both the Parties i.e. 

ASI and IA. 

4.1. Service Level Objectives 

The following Service Level Objectives have been identified for governing the SLA in e-Ticketing 


System should be available to the users always 

System should be easy to use and 

System should be responsive enough for the user to work without time delays/ 

interruptions 

Users should be able to easily store and retrieve the data from the system 

Users should always get the right kind of support as and when it is required to 

perform their work 

The system should be able to generate reports on revenue & reconciliation with 

ticket sale 

4.2. SLA Definition & Measurement 

A model SLA agreement is provided in Schedule VIII of the Master Services Agreement (MSA) in 

this Volume of the RFP. The SLA specifies the expected levels of service to be provided by the IA 

to the various stakeholders of the Project. 

The following points clarify the manner in which the SLA metrics operate: 

A set of parameters has been identified as key to ensuring the desired 

performance level of e-Ticketing system. 

The table lists out the performance level and how penalties shall be levied 

All payments to IA shall be after deduction of penalties as per the SLA metrics. 



4.3. ASI e-Ticketing Project - SLA Metrics 

The Service Level metrics that define the Service Levels and the penalties for not meeting the 

SLAs are specified in Appendix A of the Model SLA, incorporated as Schedule VIII of the MSA, in 

this Volume III of the RFP. The IA shall comply with the Service Levels specified in the said 

Appendix A. 

4.4. SLA Monitoring 

The aforementioned SLA parameters shall be monitored and measured on a 

daily/weekly/monthly/quarterly basis as per the individual SLA parameter requirements, 

through appropriate SLA Measurement tools to be designed by the IA for the purpose and 

audited by a third party for accuracy and reliability. If the performance of the system/services is 

degraded significantly at any given point in time during the Contract and if the immediate 

measures are not implemented and issues are not rectified to the complete satisfaction of ASI/ 

or an agency designated by them, then ASI will have the right to take appropriate corrective 

actions including termination of the Contract. It is to be noted that if the Penalty applicable in 

two consecutive quarters during the currency of the Contract exceeds 20% of the EQI in each 

quarter; then ASI shall have the right to terminate the Contract. 

The SLAs defined in Schedule VIII of the MSA, shall be reviewed on an annual basis by ASI after 

taking the advice of the IA, PMU and other agencies. Changes in SLA would be made by ASI 

after consultation with the IA. 



5. Draft Master Services Agreement 

Director General (DG) intends to sign 2 Agreements with the successful bidder for Design, 

Procurement, Customization, and Installation of e-Ticketing comprehensive solution and 

subsequent operation & maintenance of the e-Ticketing Solution across the country– a Master 

Services Agreement (MSA) and a Service Level Agreement (SLA). Given below is a draft of the 

MSA. Schedule VIII of the MSA provides a draft SLA. ASI may propose changes required to 

these two drafts and shall be communicated to all the bidders before the bid closing date. 

Master Services Agreement (MSA) 

This Agreement (herein afte efeed to as the /Agreement/MSA, as defied heei after) is 

made on this [Please Insert] day of 2013, by and between: 

(i) the President of India acting through the Director General (DG),Archaeological Survey of 

India, Ministry of Culture, Government of India, Janpath, New Delhi-110001 (hereinafter called 

the ASI/ DG /e-Ticketing Project) being the Party of the FIRST PART; 

AND 

(ii) ______, a company registered under the Indian Companies Act, 

1956 having its registered office at _______ and place of business at 

____(hereinafter referred to as "Implementation Agency/ IA", which expression, 

unless excluded or the context otherwise required hereof includes its successors, 

administrators and assigns) represented through its _____, 

who is duly authorized by the Implementation Agency to execute this Agreement being the 

Party of the SECOND PART. 

ASI ad Ipleetatio Age shall idepedetl e alled as Pat ad joitl as 

Paties. 

WHEREAS 

A. ASI intends to enable and augment the Design and Implementation, Management & 

Maintenance of e-Ticketing Project involving the Implementation of Software, Supply & 

Installation of System Software, Hardware and Operation & Maintenance of e-Ticketing System 

in India with the ultimate objective of ensuring transparent, easy, efficient ticketing system 

using ICT to facilitate world class Visitor experience 



B. ASI undertook selection of a suitable Implementation Agency for implementing the e- 

Ticketing Project by adopting an open tender process in three stages. The shortlisted bidders 

went through a competitive bidding issued vide a Request for Proposal (RFP) dated April 2013. 

In the first stage eligible bidders were shortlisted through Pre-Qualification criteria and in the 

second stage through technical evaluation and finally the commercial evaluation; 

C. The Implementation Agency has been selected as the successful bidder to undertake the e- 

Ticketing Project involving the development of the total solution, roll out and maintenance to 

achieve the defined objectives to ensure transparent, easy, efficient and accurate availability of 

information and facilitation of transactions; 

D. ASI intends to engage the Implementation Agency to undertake and implement the e- 

Ticketing Project on the terms and conditions set forth below. 

E. The Implementation Agency in pursuance of its proposal undertakes to implement the e- 

Ticketing Project stated herein above. 

NOW THEREFORE, IN CONSIDERATIONOF THE MUTUAL PROMISES AND COVENANTS AND 

CONDITIONS HEREIN CONTAINED, IT IS HEREBY AGREED BETWEEN THE PARTIES AS FOLLOWS:, 

ASI and the Implementation Agency have agreed to enter into this Agreement to govern the 

way in which the Implementation Agency will design, implement & manage the solution and 

facilities and deliver the services specified under this Agreement and the Service Level 

Ageeet “LA" i aodae ith oles ad esposiilities of ASI and its nominated 

agencies and the Implementation Agency as set forth in this agreement. 

5.1. Article 1 - Definitions & Interpretation 

5.1.1. Definitions 

a. In this Agreement, unless the context requires otherwise: 

Agreement" means this agreement together with all the Schedules and the 

contents and specifications of all the volumes of the Request for Proposal (RFP) 

and in all the attached schedules and any addendums, corrigendum issued and 

shall include any modifications, alterations, additions or deletions thereto agreed 

between the Parties in writing after the date hereof in terms of this Agreement. 

In the event of a conflict between this Agreement and the Schedules, the terms 

of the Agreement shall prevail; 



Project means e-Ticketing Project involving the System Design, Development, 

Implementation, Operations, Management and Maintenance across all the 

ticketed monuments of ASI as per the terms and conditions laid in the RFP and 

provision of ASI related services in conformance to the SLA; 

Customized Applicatio “oftae means the software that is readily available 

with only customization as required by ASI. This includes (except for the 

customization components on such products), proprietary software components 

and tools deployed by the Implementation Agency, and the e-Ticketing software, 

shall be solely owned by ASI; 

Confidential Information" means all information as defined in Clause 8.1.; 

"Deliverables" means the products, infrastructure and services agreed to be 

delivered by the Implementation Agency in pursuance of the Agreement as 

elaborated in Section 9.4 of the Volume I of the RFP in relation to the 

Implementation Phase and the Operations and Maintenance Phase and includes 

all documents related to the solution, user manual, technical manual, design, 

process and operating manuals, service mechanisms, policies and guidelines and 

source code and all its modifications; 

Effectie Date means the date on which the Agreement is executed by both 

the Parties. 

Itellectual Popety Rights" means rights as defined in Article VII. ; 

Mateial Beach means breach that has an effect on (a) the ability of 

Implementation Agency to perform/discharge any of its duties/obligations under 

and in accordance with the provisions of the Agreement; and/or (b) the legal 

validity, binding nature or enforceability of the Agreement; 

Pefoace Guaatee ad Pefoace Bak Guaatee shall mean the 

guarantee provided by a Nationalized Bank to ASI on behalf of the 

Implementation Agency for the amount specified in Section 6 of Vol. II of the 

RFP; 

Project means e-Ticketing Project involving the System Design, Customisation, 

supply of server/ client infrastructure,, Implementation, Operations, 

Management and Maintenance across all ticketed monument locations of ASI as 

per the terms and conditions laid down in the RFP Project Data" means all 

proprietary data of the PROJECT generated out of Project operations and 



transactions, documents and related information including but not restricted to 

user data which the Implementation Agency obtains, possesses or processes in 

the context of providing the Services to the users pursuant to this Agreement 

and the SLA;Project Locatio shall include all such ASI sites that will require 

setup of IT infrastructure including networking and backup facility for smooth 

operations of the e-Ticketing solution. 

"Poject Ipleetatio means Project Implementation as prescribed in the 

Section 9 of Volume I of the RFP; 

Project Implementation Completion Date / Final Go-Lie The Final Go live 

will be considered from 90% of successful transactions from e-Ticketing Solution 

for World heritage, Category A & B type Monuments. 

Final Go Live will be based on following Criteria: 

Successful Implementation of Online Solution,POS Solution & Handheld Solution 

fo atleast oths fo T+5 , eetig all the pesied “LAs etioed i 

RFP 

100% Reconciliation of tickets sold and cash received through all the channels 

(Online and POS) 

Closure of all the errors and bugs (Show Stopper Category) reported within 3 months 

from T+52. 

a. All the acceptance tests & certifications are successfully concluded to the 

satisfaction of ASI. 

b. "Proprietary Information" means processes, methodologies and technical and 

business information, including drawings, designs, formulae, flow charts, data 

and computer programs already owned by, or granted by third parties to a Party 

hereto prior to its being made available under this Agreement, or the SLA; 

c. RFP o Reuest fo Poposal means the documents containing the 

Technical, Functional, Operational, Commercial and Legal Specifications for the 

implementation of the Project, issued in 3 volumes (referred to as Volume I, 

Volume I Annexures, Volume II and Volume III) and includes the clarifications, 

explanations and amendments issued by ASI from time to time. 

d. "Replacement Implementation Agency" means any third party that ASI, ASI 

may appoint to replace the Implementation Agency upon expiry of the Term or 



otherwise termination of this Agreement or the SLA to undertake the Services or 

part thereof; 

e. "Service Level" means the level of service and other performance criteria which 

will apply to the Services as set out in the SLA, in Schedule VIII; 

f. “eice Leel Ageeet “LA means the Operation and Maintenance SLA, 

executed by and between Implementation Agency and ASI, in terms of the 

Service Level Requirements as per the model set out in Schedule VIII of this 

Agreement; 

g. Te means a period of 6 years from the Effective Date that shall include 1 

year of implementation phase and 5 years of Operations & Maintenance phase. 

h. "Third Party Systems" means Systems (or any part thereof) in which the 

Intellectual Property Rights are owned by a third party and to which 

Implementation Agency has been granted a license to use and which are used in 

the provision of Services; 

i. Wokig Day means any day on which any of ASI, local unit of ASI will be 

functioning, including gazetted Holidays, restricted holidays or other holidays, 

Saturdays and Sundays 

5.1.2. Interpretations 

a. References to any statute or statutory provision include a reference to that 

statute or statutory provision as from time to time amended, extended, reenacted 

or consolidated and to all statutory instruments made pursuant to it. 

b. Words denoting the singular shall include the plural and vice versa and words 

denoting persons shall include firms and corporations and vice versa. 

c. Unless otherwise expressly stated, the words "herein", "hereof", "hereunder" 

and similar words refer to this Agreement as a whole and not to any particular 

Article, Schedule. The term Articles, refers to Articles of this Agreement. The 

words "include" and "including" shall not be construed as terms of limitation. 

The words "day" and "month" mean "calendar day" and "calendar month" unless 

otherwise stated. Where, because of a difference in time zone, the calendar day 

or calendar month in one Country differs from another Country, then the 

calendar day or calendar month shall be deemed to be the calendar day or 

calendar month applicable to India. The words "writing" and "written" mean "in 

documented form", whether electronic or hard copy, unless otherwise stated. 



Any reference to attorneys' fees shall include reasonable fees of the professional 

assistants of such attorneys. 

d. The headings and use of bold type in this Agreement are for convenience only 

and shall not affect the interpretation of any provision of this Agreement. 

e. References to Clauses, Sub-Clauses, Paragraphs, Article, Schedules and 

Annexures are to clauses, sub-clauses, paragraphs, article, schedules and 

annexures to this Agreement. 

f. Use of any gender includes the other genders. 

g. ‘efeees to a opa shall e ostued so as to ilude a opa, 

corporation or other body corporate, wherever and however incorporated or 

established. 

h. ‘efeees to a peso: person shall be construed to include any individual, 

partnerships, firms, companies, corporations, joint ventures, trusts, associations, 

organizations, executors, administrators, successors, agents, substitutes and any 

permitted assignees or other entities (whether or not having a separate legal 

entity). A reference to a group of persons is a reference to all of them 

collectively, to any two or more of them collectively and to each of them 

individually. 

i. A efeee to a da iludig ithi the phase usiess da shall ea a 

period of 24 hours running from midnight to midnight. 

j. ‘efeees to a usiess da shall e ostued as a efeee to a da othe 

than a Sunday) on which banks in Delhi are generally open for business; 

k. References to times are to Indian Standard Time; 

l. A reference to any other document referred to in this Agreement is a reference 

to that other document as amended, varied, noted or supplemented at any time; 

m. Any reference at any time to any Agreement, deed, instrument, license or 

document of any description shall be construed as reference to that Agreement, 

deed, instrument, license or other document as amended, varied, supplemented, 

modified or noted at the time of such reference; 

n. Any contract, consent, approval, authorization, notice, communication, 

Information or report required under or pursuant to this Agreement from or by 



any Party and/or any other authority shall be valid and effectual only if it is in 

writing under the hands of duly authorized representative of such Party or 

authority, as the case may be, in this behalf and not otherwise; 

o. Uless otheise stated, a efeee to a peiod oeig fo a 

speified da o date ad till o util a speified da o date shall ilude 

either such days or dates; 

p. Unless otherwise specified, any interest to be calculated and payable under this 

Agreement shall accrue on an annual basis and from the respective due dates as 

provided for in this Agreement; 

q. A reference to knowledge of a person includes Information that a reasonable 

person in the circumstances of that person would have known by reasonable 

inquiry; 

In interpreting this Agreement no rule of construction applies to the disadvantage of a 

party because that party or its legal advisor was responsible for the preparation of this 

Agreement. 

5.1.3. Structure 

a. This Agreement shall operate as a legally binding services agreement specifying 

the master terms which apply to the Parties under this Agreement and to the 

provision of the Services by the Implementation Agency to the Stakeholders of 

the Project under the duly executed SLA. 

b. The SLA in respect of the Operation and Maintenance is being entered into 

concurrently with this Agreement between the Implementation Agency and ASI. 

In respect of any future SLAs entered into between the Parties, each of the 

Parties shall observe and perform the obligations set out herein. 

c. In the event of a change of Control of the Implementation Agency during the 

currency of this Agreement. Implementation Agency shall promptly notify ASI of 

the same and in the event that the net worth of the surviving entity is less than 

that of Implementation Agency prior to the change of Control, ASI may within 30 

days of his/ her becoming aware of the change in Control, require a replacement 

of existing Performance Guarantee furnished by the Implementation Agency 

from a guarantor acceptable to ASI (which shall not be Implementation Agency 

or any of its associated entities). If such a guarantee cannot be obtained within 

30 days of ASI becoming aware of the change in Control, he/ she may exercise its 



right to terminate the SLA within a further 30 days by written notice, to become 

effective when specified in such notice. Pursuant to termination, the 

consequences of termination as set out in Article 5.2 hereinafter will become 

effective. The internal reorganization of the Implementation Agency shall not be 

deemed an event of a change of Control for purposes of this Article unless the 

surviving entity is of less net worth than the predecessor entity. 

d. The SLA shall be a separate divisible contract in respect of this Agreement. 

e. The Project engagement which includes the scheduled Project Implementation 

Phase will be governed by the acceptance and testing criteria which will have ASI 

and/or a technically competent agency or agencies for conducting the 

acceptance and testing certifications simultaneously with the triggering of the 

Project Phases in the manner herein below: 

i. ASI will nominate a technically competent agency/person for conducting 

acceptance testing and certification. 

ii. The agency/person will lay down a set of guidelines following internationally 

accepted norms and standards for testing and certification in all aspects of 

project development and implementation covering software, hardware and 

networking including the processes relating to the design of solution 

architecture, design of systems and subsystems, coding, testing, business 

process description, documentation, version control, change control, 

security, service oriented architecture, performance in relation to compliance 

with SLA, metrics, interoperability, scalability, availability and compliance 

with all the technical and functional requirements of the RFP and this 

Agreement. 

iii. The agency/person will be involved with Project early in the development 

stage to ensure that the guidelines are being followed and to avoid large 

scale modifications pursuant to testing done after the application is fully 

developed. 

iv. The agency/person nominated by ASI can engage professional organizations 

for conducting specific tests on the software, hardware, networking, security 

and all other aspects. 

v. The agency/person will establish appropriate processes for notifying the IA of 

any deviations from the norms, standards or guidelines at the earliest 



instance after taking cognizance of the same to enable the IA to take 

corrective action. 

vi. Such an involvement of and guidance by the agency/person will not, however 

absolve the IA of the fundamental responsibility of designing, 

developing,installing, testing and commissioning the various components of 

the Project to deliver the services in perfect conformity with the SLA. 

5.1.4. Conditions Precedent 

Subject to express terms to the contrary, the rights and obligations under this 

Agreement shall take effect only upon fulfillment of all the Conditions Precedent set out 

below in Articles 1.4.1 and 1.4.2 hereinafter efeed as Coditio Peedets. 

However, ASI or its nominated agencies may at any time at its sole discretion waive fully 

or partially any of the Conditions Precedents for the Implementation Agency. 

5.1.4.1. The following Conditions Precedent need to be fulfilled by the 

Implementation Agency on or before the execution of this Agreement: 

a. Provide Performance Bank Guarantee specified in Volume II of the RFP in the 

form of a Bank Guarantee for an amount being equivalent to 10% of the total 

contract value as quoted in the commercial proposal as specified in Annexure 

of Vol II of this RFP, to ASI; 

b. Provide ASI or its nominated agencies certified true copies of its 

constitutional documents and board resolutions authorizing the execution, 

delivery and performance of this Agreement and the SLA with ASI; 

5.1.4.2. The following Conditions Precedent need to be fulfilled by the 

Implementation Agency on or before the beginning of Operation & 

Maintenance Phase: 

a. IA shall have completed the testing, operation and commissioning of the 

solution and successful completion as mentioned in the Implementation 

Schedule to the satisfaction of ASI. 

b. IA shall have completed the testing, operation and commissioning of the e- 

Ticketing Application at specified locations by the date as provided in the 

Implementation Schedule. 



c. IA shall obtain certificates of compliance 15 (fifteen) days prior to the Final 

Go-Live to ensure that the aforesaid Conditions Precedent as set forth in (a) 

and (b) above have been duly satisfied. 

5.1.5. Non-fulfillment of Conditions Precedent 

a. In the event that any of the Conditions Precedent relating to Implementation 

Agency has not been fulfilled, as per the Implementation Schedule as set out 

in Schedule IX and the same has not been waived by ASI fully or partially, this 

Agreement shall cease to have any effect as of that date. 

b. In the event that the Agreement fails to come into effect on account of nonfulfillment 

of the Implementation Agency's Conditions Precedent, ASI shall 

not be liable in any manner whatsoever to the Implementation Agency and 

ASI shall forthwith invoke the Performance Guarantee and forfeit the 

guaranteed amount. 

c. In the event that vacant possession of any of the Project facilities and/or 

Project Data has been delivered to the Implementation Agency prior to the 

fulfillment in full of the Conditions Precedent, upon the termination of this 

Agreement such Project facilities and Project data shall immediately revert to 

ASI free and clear from any encumbrances or claims. 

d. Instead of terminating this Agreement as provided in paragraph 1.4.2(a) 

above, the Parties may mutually agree in writing to extend the time for 

fulfilling the Conditions Precedent and the Term of this Agreement. It is 

further clarified that any such extension of time shall be subject to imposition 

of penalties on IA linked to the delay in fulfilling the Conditions Precedent.. 

5.2. Article II – Initialization Phase 

5.2.1. Scope Of Agreement 

This Agreement shall govern the provision of the contractual professional services, 

listed hereunder and morefully described in Volume I of the RFP, in conformance 

with the SLA, to all the stakeholders of the e-Ticketing Project. It is anticipated that 

new or renewal agreements may be undertaken by creating a separate SLA, with 

schedules and exhibits as required, under this Agreement for each engagement. 

Services to be provided by the IA under the Agreement: 

The e-Ticketing project broadly covers the following activities: 



a. Study, design, customization testing, and deployment of a web-based eticketing 

system, integrated with payment gateway, to enable visitors to 

pre-book tickets on internet at their convenience. 

b. Supply, installation, configuration, customization, integration, testing and 

commissioning of Point-of-Sale (POS) application at ticketed monuments 

that shall have a common back-end platform that integrates with a 

common solution. 

c. Procurement, installation, configuration and commissioning of client side IT 

and non-IT infrastructure 

d. Deployment of server side application including IT and non-IT infrastructure 

at the DC-DR that is either owned by the IA or through a third party 

arrangement by IA. 

e. Facilitate ASI in provisioning, configuration and commissioning of network 

links to all the identified monument sites of ASI that enables connectivity to 

the Data Center and Disaster Recovery Center 

f. Supply of manpower services to manage and operate the ticketing system 

at ticket issuing counters and entry gates 

g. Operation and Maintenance of the entire e- Ticketing System including 

Application, IT & Non-IT infrastructure for a period of five years from the 

date of final Go-Live 


5.2.2. Interpretation of the Scope of Work 

a. ASI retains the right of the final say in the interpretation of the scope of the 

Project. The possible variations to the processes from the way they are 

specified in the scope of work should not be considered as deviations or 

extensions to the original process specifications. 

b. Sign-off on the Deliverables by ASI does not necessarily indicate the 

complete approval of the Deliverables. All the responsibilities with respect 

to operations and maintenance of the existing applications, infrastructure 

or requirements in the RFP or ASI processes will be the responsibility of the 

Implementation Agency. Any gap that is found in a deliverable with respect 

to the above, even after the sign-off, will have to be addressed by the 

Implementation Agency without any additional cost to ASI. 

c. The performance of the ultimate system can be achieved by different 

combinations of the equipment and network components. The final 

acceptance of the integrated solution and infrastructure components 



should be as per the performance requirements and will be the determining 

factor but not the specifications of the infrastructure alone. 

5.2.3. Period Of Agreement 

The Term of the permission/ license under the MSA shall be for a period of 6 years 

from the date of signing of the Agreement that shall include 1 year of 

implementation phase and 5 years of Operations & Maintenance phase. However, 

ASI may choose to extend the Term for a maximum period of two years in mutual 

consultations with the IA with all the terms and conditions of original Agreement. A 

fresh tender shall be called at the end of the Term/ extended term. The bid process 

for the second term shall commence one year before the expiry of the Term / 

extended term. 

5.2.4. Commencement And Duration Of This Agreement 

This Agreement shall come into effect on fulfillment of the conditions precedent 

specified in section 1.4.1 and certified as such by ASI (hereinafter called the 

Effetie Datead shall, sujet to the aiu tie liit of 6 years. Any 

extension of Agreement term if so shall be decided by ASI . 

5.2.5. Scope And Provision Of The Services 

a. The provision of Services to the Stakeholders with certainty and speed is the 

essence of the Agreement between the Parties. 

b. The Implementation Agency represents that it is a competent and efficient 

provider of a variety of information technology and business process 

management services. Implementation Agency will keep abreast of the relevant 

technical, managerial and operational requirements applicable to the provision 

of the Services and best practices in this area and will share their knowledge 

with ASI, regarding matters which would assist ASI in its use of the Services, 

provided that Implementation Agency shall not be obligated to share other 

client information or Confidential Information of Implementation Agency not 

relevant to this Agreement. 

c. The Services shall be performed by the Implementation Agency pursuant to 

terms under the SLA to be entered into in accordance with this Agreement. 

d. The Implementation Agency shall perform the Services (a) in a good 

professional manner commensurate with professional industry and technical 

standards which are generally in effect for international projects and 

innovations pursuant thereon similar to those contemplated by this Agreement, 



(b) so as to comply with the applicable Service Levels and (c ) in accordance 

with the terms set out in this Agreement and the SLA. 

The Parties shall ensure that the range of the Services under the SLA shall not be varied, 

reduced or increased except by the prior written agreement of ASI in accordance with the 

Change Control Schedule. Save, for the express terms of the Terms of Payment Schedule, 

ASI and its users shall be obliged to purchase any particular category of Services that may 

become necessary as per the Change Control Schedule from the IA, without the need to go 

for a separate procurement process. 

e. In providing the Services, IA shall ensure not to cause any unnecessary 

disruption to the ASIs oal business operations. 

f. No Party to this Agreement or to the SLA will at any time perform, or omit to 

perform, any act which they are aware, at the time of performance, will place 

the other Party in default under any insurance policy, mortgage or lease, 

governing activities at any location provided by ASI. 

5.2.6. Commencement And Duration Of the Sla 

a. The Operation and Maintenance SLA will commence from the date Fial Go 

Lie when the Project Implementation has been completed to the satisfaction 

of ASI, and certified in accordance with the terms of this Agreement and shall 

run for a period coterminous with the MSA. 

b. The SLA shall commence on the date on which it is fully executed by ASI and the 

Implementation Agency and shall, unless terminated earlier in accordance with 

its terms or unless otherwise agreed by the Parties, expire on the date on which 

this Agreement expires or terminates for any reason. 

5.2.7. Approvals And Required Consents 

a. The Parties will cooperate reasonably to obtain, maintain and observe all 

relevant and customary regulatory and governmental licenses, clearances and 

appliale appoals heeiafte the Appoals eessa fo the 

Implementation Agency to provide the Services. The costs of such Approvals 

shall be borne by the Implementation Agency. 

b. Both parties will give each other all co-operation and information reasonably 

required to meet their respective obligations under this Agreement. 

c. ASI shall use reasonable endeavors to assist Implementation Agency obtain the 

Approvals. In the event that any Approval is not obtained, the Implementation 

Agency and ASI will co-operate with each other in achieving a reasonable 



alternative arrangement as soon as reasonably practicable for ASI to continue 

to process its work with as minimal interruption to its business operations as is 

commercially reasonable until such Approval is obtained, provided that the 

Implementation Agency shall not be relieved of its obligations to provide the 

Services and to achieve the Service Levels until the Approvals are obtained if 

and to the extent that the Implementation Agency's obligations are dependent 

upon such Approvals. 

5.2.8. Use And Acquisition Of Assets 

During the Term of the MSA, the Implementation Agency shall: 

a. Take all reasonable and proper care of the entire hardware and software, 

network or any other information technology infrastructure components used 

for the Project and other facilities leased / owned by the Implementation 

Agency exclusively in terms of the delivery of the Services as per this 

Ageeet heeiafte the Assets i popotio to thei use ad otol of 

such Assets which will include all upgrades/ enhancements and improvements 

to meet the current needs of the Project; and 

b. Keep all the tangible Assets in as good and serviceable condition and/or the 

intangible Assets suitably upgraded subject to the relevant standards as stated 

in Volume I of the RFP as at the date the Implementation Agency takes control 

of and/ or first uses the Assets and during the entire Term of the Agreement; 

and 

c. Ensure that any instructions or manuals supplied by the manufacturer of the 

Assets for use of the Assets and provided to the Implementation Agency will be 

followed by the Implementation Agency and any person who will be 

responsible for the use of the Assets; and 

d. Take such steps as may be properly recommended by the manufacturer of the 

Assets and notified to the Implementation Agency or as may, in the reasonable 

opinion of the Implementation Agency, be necessary to use the Assets in a safe 

manner; and 

e. To the extent that the Assets are under the control of the Implementation 

Agency, keep the Assets suitably housed and in conformity with any statutory 

requirements from time to time applicable to them; and 

f. Procure permission from ASI and any persons duly authorized by him/ her to 

enter any land or premises on which the Assets are for the time being sited so 

as to inspect the same, subject to any reasonable third party requirements; and 



g. Not knowingly or negligently use or permit any of the Assets to be used in 

contravention of any statutory provisions or regulation or contrary to law; and 

h. Use the Assets exclusively for the purpose of providing the Services as 

appropriate; and 

i. Not sell, offer for sale, assign, mortgage, pledge, sub-let or lend out any of the 

Assets; and 

j. Use the Assets only in accordance with the terms hereof and those contained in 

the SLA; and 

k. Obtain and/ or maintain standard forms of comprehensive insurance policy 

including liability insurance, system and facility insurance and any other 

insurance for the personnel, Assets, data, software, etc.; and 

l. Transfer the ownership of all the Assets (not already with ASI, including but not 

limited to the project documentation which is the work product of the 

development efforts involved in the Project) within 30 days of the acceptance 

of the same by ASI upon testing and/ or audit , to ASI in accordance with the 

terms of this Agreement; and 

m. To ensure the integration of the software with hardware to be installed and the 

current Assets in order to ensure the smooth operations of the entire solution 

architecture to provide efficient services to all the Stakeholders of Project in an 

efficient and speedy manner; and 

n. To provide a well-prepared documentation for users manual, a clear plan for 

training, educating and hand holding the users and shall form part of 

handholding phase until bringing up to speed; and 

o. Train the team identified by ASI, which will be in place during hand-holding and 

will be responsible for trouble shooting all post-implementation maintenance 

activities; and 

p. An approval (i.e. sign off) from ASI at each stage is essential to close each of the 

above considerations. 

5.2.9. Access To Implementation Agency Or Its Nominated Agencies To ASI Location 

a. For so long as the Implementation Agency provides Services from any Project 

location on a non-permanent basis and to the extent necessary for the 

Implementation Agency to provide the Services and at no cost to the 

Implementation Agency, ASI, shall, subject to compliance by the Implementation 

Agency with any safety and security guidelines which may be notified by ASI to 

the Implementation Agency in writing, provide the Implementation Agency with: 



(i) Reasonable access, in the same manner granted to ASI employees, to ASI 

locations twenty-four hours a day, seven days a week; and 

(ii) Access to office equipment as mutually agreed and other related support 

services in project location and at other ASI locations, if any, as may be 

reasonably necessary for the Implementation Agency to perform its obligations 

hereunder and under the SLA. 

b. Locations and items shall be made available to the Implementation Agency on an 

"as is, where is" basis ASI as per the time schedule agreed upon between the 

parties. The Implementation Agency agrees to ensure that its employees, agents 

and contractors use these locations solely for performing the bonafide Project 

activities and do not use the location, services and items : 

(i) For the transmission of any material which is defamatory, offensive or abusive 

or of an obscene or menacing character; or 

In a manner which constitutes a violation or infringement of the rights of any 

person, firm or company (including but not limited to rights of copyright or 

confidentiality). 

5.3. Article III - Management Phase 

5.3.1. Governance 

The review and management process of this Agreement shall be carried out in 

accordance with the Governance Schedule (Schedule IV of this Agreement) and 

shall cover all the management aspects as set out in the RFP. 

5.3.2. Use Of Services 

a. ASI, or its nominated agencies will undertake and use the Services in 

accordance with the terms of this Agreement for such usage and mutually 

agreed by the Parties from time to time. 

b. ASI, or its nominated agencies will use the Deliverables resulting from the 

Services provided by or on behalf of the IA. 

5.3.3. Changes 

Unless expressly dealt with elsewhere in this Agreement, any changes under or to this 

Agreement or under or to the SLA shall be dealt with in accordance with the Change 

Control Schedule (Schedule I of this Agreement). 



5.3.4. Security And Safety 

a. The Implementation Agency will comply with the directions issued from time to 

time by ASI and the standards related to the security as stated in RFP Volume I, 

in so far as it applies to the provision of the Services. 

b. Each Party to the SLA shall also comply with Projects ifoatio teholog 

security standards and policies in vogue from time to time at each location of 

which ASI makes the Implementation Agency aware in writing insofar as the 

same apply to the provision of the Services. 

c. The Parties to the SLA shall use reasonable endeavors to report forthwith in 

writing to each other all identified attempts (whether successful or not) by 

unauthorized persons (including unauthorized persons who are employees of 

any Party) either to gain access to or interfere with the Project's data, facilities or 

Confidential Information. 

d. The Implementation Agency shall upon request by ASI or its nominee(s) 

participate in regular meetings when safety and information technology security 

matters are reviewed. 

e. The Parties under the SLA shall promptly report in writing to each other any act 

or omission which they are aware that could have an adverse effect on the 

pope odut of safet ad ifoatio teholog seuit at Pojets 

locations. 

5.3.5. Co-Operation 

a. Except as otherwise provided elsewhere in this Agreement or the SLA, each Party 

("Providing Party") to this Agreement or to the SLA undertakes promptly to 

provide the other Party ("Receiving Party") with all such information and cooperation 

which the Receiving Party reasonably requests, provided that such 

information and co-operation: 

(i) is reasonably required by the Receiving Party in order for it to comply with 

its obligations under this Agreement or the SLA; and 

(ii) is not Confidential Information; and 

(iii) is capable of being provided by the Providing Party. 



b. Each Party agrees to co-operate with the contractors and sub-contractors of the 

other Party as reasonably requested in order to accomplish the purposes of this 

Agreement. 

5.4. Article IV - Financial Issues 

5.4.1. Terms Of Payment And Service Debits 

a. In consideration of the Services and subject to the provisions of this Agreement 

and of the SLA, ASI shall pay the Implementation Agency for the Services 

rendered in pursuance of this Agreement, in accordance with the Terms of 

Payment Schedule (Schedule VI of this Agreement). 

b. All payments are subject to the application of service debits and liquidated 

damages defined and provided for in this Agreement and the SLA. It is clarified 

here that ASI will calculate a financial sum and debit the same against the terms 

of payment as defined in the Terms of Payment Schedule as a result of the 

failure of the Implementation Agency to meet the Service Level under the SLA, 

such sum being determined in accordance with the terms set out in this 

Agreement and the SLA. 

c. Except as otherwise provided for herein or as agreed between the Parties in 

writing, ASI shall not be required to make any payments in respect of the 

Services other than those covered by the terms of payment as stated in the 

Terms of Payment Schedule (Schedule VI of this Agreement). 

5.4.2. Invoicing And Settlement 

5.4.3. Tax 

The provisions of the Invoicing & Settlement Schedule (Schedule V of this 

Agreement) shall apply. 

a. ASI shall withhold taxes from the amounts due and payable to the 

Implementation Agency wherever applicable. The Implementation Agency shall 

pay for all other taxes in connection with this Agreement, and SLA including, 

but not limited to, property, sales, use, excise duty, value-added, goods and 

services, consumption and other similar taxes or duties. ASI shall provide 

Implementation Agency with the original tax receipt of any withholding taxes 

paid by Project on payments under this Agreement. The Implementation 

Agency agrees to reimburse and hold ASI harmless from any deficiency 



(including penalties and interest) relating to taxes that are its responsibility 

under this paragraph. For the purposes of this Agreement, taxes shall include 

taxes incurred on services rendered to ASI, the Implementation Agency and any 

third party subcontractors. The Service Tax incurred on the services provided to 

ASI shall be borne by ASI. 

b. In the event of any increase or decrease of the rate of taxes due to any 

statutory notification/s during the Term of the Agreement the consequential 

effect shall be to the account of the Implementation Agency. 

c. The Parties shall cooperate to enable each Party to accurately determine its 

own tax liability and to minimize such liability to the extent legally permissible. 

In connection therewith, the Parties shall provide each other with (i) any resale 

certificates, (ii) any relevant information regarding use of out-of-state 

materials, equipment or services and (iii) any exemption certificates or 

information reasonably requested by the other Party. 

5.4.4. Liquidated Damages: 

I the eet of IAs failue to, suppl the Assets ad odut tials, istallatio of 

equipment and training as per RFP, ASI may at his discretion withhold any 

payment until the completion of the Agreement. ASI may also deduct from IA as 

agreed, liquidated damages Liquidated Damages to the sum of 0.5% of the 

corresponding milestone payment of delayed/undelivered stores/ services 

mentioned above for every week of delay or part of a week, subject to the 

maximum value of the Liquidated Damages being not higher than 10% of the 

value of corresponding milestone payment of the delayed/undelivered services. 

This right to claim any liquidated damages shall be without prejudice to other 

rights and remedies available to ASI under the Agreement and/or any other law. 

5.5. Article V - Breach, Rectification& Termination 

5.5.1. In the event that the Implementation Agency is in Material Breach of its 

obligations under this Agreement or the SLA, ASI may terminate this Agreement or 

the SLA upon notice to the other Party. Any notice served pursuant to this Article 

shall give reasonable details of the Material Breach, which could include the 

following events and the termination will become effective: 



i. If there is Breach which translates into default in providing Services by the 

Implementation Agency as per this Agreement or the SLA, continuously for more 

than one week, then ASI, will serve a seven das otie for curing such Material 

Breach. In case the Material Breach continues after the notice period, ASI will 

have the option to terminate the Agreement. 

ii. Because time is the essence of the contract, in case, for reasons prima facie 

attributable to the Implementation Agency, there is a delay of more than 4 

weeks in the Project Implementation Phase by the Implementation Agency prior 

to the acceptance testing and certification stage, ASI may terminate this 

Agreement after affording a reasonable opportunity to the Implementation 

Agency to explain the circumstances leading to such a delay. Further, ASI may 

also invoke the Performance Guarantee of the Implementation Agency. Pursuant 

to the termination, IA shall transfer all the assets to ASI as set out in clause 2.7.l, 

in this volume of the RFP. 

5.5.2. Where a change of control of the Implementation Agency has occurred whereby 

the Implementation Agency-company has merged, amalgamated or been taken 

over, due to which the majority shareholding of the Implementation Agency has 

been transferred to another entity, ASI can by a 60days written notice, terminate 

this Agreement and such notice shall become effective at the end of the notice 

period. 

5.5.3. Termination 

a. ASI may serve written notice on Implementation Agency at any time to terminate 

this Agreement with immediate effect in the event of a reasonable apprehension of 

bankruptcy of the Implementation Agency: 

(i) Implementation Agency shall in the event of an apprehension of bankruptcy 

immediately inform ASI well in advance (at least 3 months) about such a 

development; 

(ii) Conversely if ASI apprehends a similar event regarding the Implementation 

Agency, he/ she can exercise the right of termination in the manner stated 

hereinabove. 

b. If the performance of the system/services is degraded significantly at any given point 

in time during the Agreement and if the immediate measures are not implemented 

and issues are not rectified to the complete satisfaction of ASI or an agency 



designated by them, then ASI will have the right to take appropriate corrective 

actions including termination of the Agreement. It is to be noted that if the Penalty 

applicable in two consecutive quarters during the currency of the Agreement 

exceeds 20% in each quarter; then ASI shall have the right to terminate the 

Agreement. 

c. Fraud by the IA –ASI reserves its right to initiate criminal action against the IA for 

fraud or misappropriation, under the applicable laws besides stringent penalties and 

ASI shall have the right to initiate action for termination of Agreement if ASI finds it 

necessary to do so. 

d. On termination of this Agreement for any reason, the SLA shall automatically 

terminate forthwith and ASI will decide the appropriate course of action. 

e. The termination provisions set out in Article V of this Agreement shall apply to the 

“LA ad this Ageeet shall e deeed to refer to the SLA. 

5.5.4. Effects Of Termination 

a. In the event that ASI, terminates this Agreement pursuant to Article 5.1 and 

depending on the event of default, compensation will be decided in accordance with 

the terms of Payment Schedule (Schedule VI of this Agreement). 

b. Upon termination of this Agreement, the Parties will comply with the Exit 

Management Schedule (Schedule II of this Agreement). 

5.5.5. Fraud by IA’s pesoel 

ASI reserves its right to initiate criminal action against the agents/ employees of 

the IA for fraud or misappropriation, besides stringent penalties. The management 

of the IA would also be made liable for action in case of fraud, under the applicable 

laws and ASI may call for termination of the Contract if ASI finds it necessary to do 

so. 

5.6. Article VI - Protection And Limitations 

5.6.1. Warranties 

a. The Implementation Agency warrants and represents to ASI that: 

(i) it has full capacity and authority and all necessary approvals to enter into 

and to perform its obligations under this Agreement; 



(ii) this Agreement is executed by a duly authorized representative of 

Implementation Agency; 

(iii) it shall discharge its obligations under this Agreement with due skill, care and 

diligence so as to comply with Article 2.4. 

b. In the case of the SLA, the Implementation Agency warrants and represents to 

ASI, that: 

(i) the Implementation Agency has full capacity and authority and all necessary 

approvals to enter into and perform its obligations under the SLA and to 

provide the Services; 

(ii) the SLA has been executed by a duly authorized representative of the 

Implementation Agency; 

(iii) the Implementation Agency is experienced in managing and providing works 

similar to the Services and that it will perform the Services with all due skill, 

care and diligence so as to comply with Article 2.4; 

(iv) the Services will be provided and rendered by appropriately qualified, 

trained and experienced personnel; 

(v) Implementation Agency has and will have all necessary licenses, approvals, 

consents of third parties and all necessary technology, hardware and 

software to enable it to provide the Services; 

(vi) the Services will be supplied in conformance with all applicable laws, 

enactments, orders and regulations; 

(vii) Implementation Agency will use its reasonable endeavors to ensure that the 

equipment, software and hardware supplied and/or used in the course of 

the provision of the Services, save for the Assets, are operational and 

functional; and 

(viii) if Implementation Agency uses, in the course of the provision of the Services, 

components, equipment, software and hardware manufactured by any third 

party which are embedded in the Deliverables or are essential for the 

successful use of the Deliverables, it will pass through third party 

manufacturer's warranties relating to those components, equipment, 

software and hardware to ASI to the extent possible. In the event that such 

warranties cannot be enforced by ASI, the Implementation Agency will 



enforce such warranties on behalf of ASI and pass on to ASI, the benefit of 

any other remedy received in relation to such warranties. 

(ix) Notwithstanding what has been stated elsewhere in this Agreement and the 

Schedules attached herein, in the event the Implementation Agency is 

unable to meet the obligations pursuant to the implementation of the , 

Project, Operations and Maintenance Services and any related scope of work 

as stated in this Agreement and the Schedules attached herein, ASI will have 

the option to invoke the Performance Guarantee after serving a written 

notice fifteen days in advance on the Implementation Agency. 

5.6.2. Third Party Claims 

a. Subject to Article 6.2b below, Implementation Agency (the "Indemnifying 

Party") undertakes to indemnify ASI (the "Indemnified Party") from and 

against all losses, claims or damages on account of bodily injury, death or 

damage to tangible personal property and otherwise caused by its 

negligence/ fraud/willful misconduct, arising in favor of any person, 

corporation or other entity (including the Indemnified Party) attributable to 

the Indemnifying Party's performance or non-performance under this 

Agreement or the SLA. 

b. The indemnities set out in Articles 6.2a shall be subject to the following 

conditions: 

(i) the Indemnified Party, as promptly as practicable, informs the 

Indemnifying Party in writing of the claim or proceedings and provides 

all relevant evidence, documentary or otherwise; 

(ii) the Indemnified Party shall, at the cost of the Indemnifying Party, give 

the Indemnifying Party all reasonable assistance in the defense of such 

claim including reasonable access to all relevant information, 

documentation and personnel provided that the Indemnified Party may, 

at its sole cost and expense, reasonably participate, through its 

attorneys or otherwise, in such defense; 

(iii) if the Indemnifying Party does not assume full control over the defense 

of a claim as provided in this Article, the Indemnifying Party may 

participate in such defense at its sole cost and expense, and the 

Indemnified Party will have the right to defend the claim in such manner 



as it may deem appropriate, and the cost and expense of the 

Indemnified Party will be included in Losses; 

(iv) the Indemnified Party shall not prejudice, pay or accept any proceedings 

or claim, or compromise any proceedings or claim, without the written 

consent of the Indemnifying Party; 

(v) all settlements of claims subject to indemnification under this Article 

will: (a) be entered into only with the consent of the Indemnified Party, 

which consent will not be unreasonably withheld and include an 

unconditional release to the Indemnified Party from the claimant for all 

liability in respect of such claim; and (b) include any appropriate 

confidentiality agreement prohibiting disclosure of the terms of such 

settlement; 

(vi) the Indemnified Party shall account to the Indemnifying Party for all 

awards, settlements, damages and costs (if any) finally awarded in favor 

of the Indemnified Party which are to be paid to it in connection with 

any such claim or proceedings; 

(vii) the Indemnified Party shall take legally permissible steps that the 

Indemnifying Party may reasonably require to mitigate or reduce its loss 

as a result of such a claim or proceedings; and 

(viii) in the event that the Indemnifying Party is obligated to indemnify an 

Indemnified Party pursuant to this Article, the Indemnifying Party will, 

upon payment of such indemnity in full, be subrogated to all rights and 

defenses of the Indemnified Party with respect to the claims to which 

such indemnification relates; 

5.6.3. Limitation Of Liability 

The IAs aggegate liailit fo daages shall e apped at % of the alue of the Ageeet 

provided that this limit shall not apply to 

(i) The bodily injury (including death) and damage to real property and tangible 

personal property caused by IA's negligence/ fraud/willful misconduct 

and/or 

(ii) The intellectual property infringement claims as per Article VII. 



a. IA shall not in any event be liable for any indirect or consequential damages 

except with respect to the bodily injury (including death) and damage to real and 

tangible personal property caused by IA's negligence/ fraud/willful misconduct. 

b. Neither this Agreement nor the services delivered by IA under this Agreement 

grants or creates any rights, benefits, claims, obligations or causes of action in, to 

or on behalf of any person or entity (including any third party) other than 

between the respective Parties to this Agreement, as the case may be. 

c. Title and Risk of Loss. IA shall bear the risk of loss on Assets up to the time they 

are transferred and handed over to ASI - after which it shall stand transferred to 

ASI. IA shall arrange and pay for insurance to cover such item until it is 

transferred and even after the transfer of the Assets till the insurance policies 

come up for a renewal. 

d. Notwithstanding what has been stated elsewhere in this Agreement and the 

Schedules attached herein, ASI shall not be liable to IA for any indirect or 

consequential damages. 

e. Any claim or series of claims arising out or in connection with this Agreement or 

the SLA shall be time barred and invalid if legal proceedings are not commenced 

by the relevant Party against the other Party within such period as may be 

permitted by applicable law without the possibility of contractual waiver or 

limitation. 

f. ASI shall be entitled to claim the remedy of specific performance under this 

Agreement or the SLA. 

5.6.4. Data Protection 

a. In the course of providing the Services the Implementation Agency may be 

compiling, processing and storing proprietary Project Data relating to the users. 

b. The Implementation Agency and each user are responsible for complying with its 

respective obligations under the applicable data protection laws and regulations 

governing the Project Data. 

c. As a processor of Project Data, the Implementation Agency will process Project 

Data in accordance with the terms of this Agreement or the SLA. 

d. The Implementation Agency shall not transfer any Project Data to any entity 

unless otherwise authorized by ASI in this regard. 



e. Upon reasonable written request from a Party to the MSA or the SLA, the other 

Party to the SLA will provide the requesting Party with such information that it 

has regarding the Project, Data and its processing which is necessary to enable 

the requesting party to comply with its obligations under the applicable data 

protection law or regulation. 

5.6.5. Audit, Access And Reporting 

a. The Parties shall comply with the Audit, Access and Reporting Schedule provided 

in Schedule III. 

b. The Implementation Agency shall, on request, allow access to ASI and its 

nominees to all information which is in the possession or control of the 

Implementation Agency, which relates to the provision of the Services as set out 

in the Audit, Access and Reporting Schedule and is reasonably required to 

comply with the terms of the Audit, Access and Reporting Schedule. 

5.7. Article VII - Intellectual Property 

5.7.1. Intellectual Property 

a. Except to the extent otherwise expressly provided in this Agreement, ASI shall 

retain exclusive intellectual property rights to the e-Ticketing software, forms 

and the compilations of the Project to which ASI has sovereign rights and 

nothing herein shall or will be construed or deemed to grant to the 

Implementation Agency any right, title, license, sub-license, proprietary right or 

other claim against or interest in, to or under (whether by estoppels, by 

implication or otherwise) to the aforesaid rights. A copy of the source code of 

the customized e-Ticketing Software (ETS) shall be kept in the custody of ASI / 

PMU on a monthly basis, with proper version control. 

b. For all the reusable components whose source code and IPR vest with the 

original owner, the licenses for such ETS applications shall be in the name of ASI. 

ASI shall retain exclusive intellectual property rights to, customized 

enhancements of the eTS application, forms and the compilations of the Project 

to which ASI has sovereign rights and nothing herein shall or will be construed or 

deemed to grant to the Implementation Agency any right, title, license, sublicense, 

proprietary right or other claim against or interest in, to or under 

(whether by estoppels, by implication or otherwise) to the aforesaid rights. 



c. Without limiting the generality of Article 7.1a and except to the extent otherwise 

expressly agreed by the Parties to this Agreement or the SLA in writing, nothing 

contained in this Agreement or the SLA shall or will be construed or deemed to 

grant to the Implementation Agency any right, title, license or other interest in, 

to or under (whether by estoppels, by implication or otherwise) any logo, 

trademark, trade name, service mark or similar designations of ASI or Project or 

its respective affiliates/nominees or any confusingly similar designations of 

Project . 

d. Subject to any sole or exclusive rights granted by ASI to a third party prior to the 

Effective Date, ASI grants to the Implementation Agency and any sub-contractors 

to the Implementation Agency solely in their performance of Services for Project 

, non-exclusive, limited, paid-up, royalty-free license during the Term of this 

Agreement, but not the right to sub-license, to use the Project Data including 

the right to copy, perform, display, execute, reproduce, modify, enhance and 

improve the Project Data to the extent reasonably necessary or useful for the 

provision of Services hereunder. 

e. Implementation Agency shall not use the Project Data to provide services for the 

benefit of any third party, as a service bureau. 

f. Implementation Agency shall indemnify, defend and hold harmless ASI and their 

respective officers, employees, successors and assigns, from and against any and 

all losses arising from claims by third parties that any Deliverables (or the access, 

use or other rights thereto) created by Implementation Agency pursuant to this 

Agreement, and/or the SLA, or any equipment, software, information, methods 

of operation or other intellectual property (or the access, use or other rights 

thereto) provided by Implementation Agency or sub-contractors to the 

Implementation Agency pursuant to this Agreement or the SLA (i) infringes a 

copyright enforceable in India, (ii) infringes a patent issued in India, or (iii) 

constitutes misappropriation or unlawful disclosure or use of another Party's 

trade secret under the laws of India (collectively, "Infringement Claims"); 

provided, however, that this will not apply to any Deliverables (or the access, use 

or other rights thereto) created by (A) ASI ; (B) third parties (i.e., other than 

Implementation Agency or Implementation Agency's sub-contractors) at the 

direction of ASI. 

g. ASI shall have no liability or obligation to Implementation Agency or any other 

Party under Article 7.1e above to the extent the Infringement Claim is based 



upon any use of the equipment, software, information, methods of operation or 

other intellectual property (or the access, use or other rights thereto) for the 

benefit of any Party (including any use by Implementation Agency or its 

nominees outside the scope of the Services) other than for Project. 

h. Notwithstanding any provisions of this Agreement to the contrary, the foregoing 

remedies constitute the Parties' sole and exclusive remedies and each Party's 

entire liability, with respect to Infringement Claims. 

i. If Implementation Agency uses in the course of the provision of the Services any 

Third Party System it will use all commercially reasonable endeavors to pass 

through to ASI such third party's warranties relating to such Third Party Systems. 

In the event that such warranties cannot be passed through to or enforced by 

ASI the Implementation Agency will enforce such warranties on A“Is behalf and 

account to ASI for so doing. 

j. All rights, title and interest in and to, and ownership in, Proprietary Information 

of Project which is provided to Implementation Agency, and all modifications, 

enhancements and other derivative works of such Project Proprietary 

Information ("Project Proprietary Information"), as a result of Services rendered 

by the Implementation Agency hereunder shall remain solely with ASI. 

Implementation Agency shall be entitled to use such Project Proprietary 

Information only during the Agreement Term and only for the purposes of 

providing the Services or to the extent necessary for Implementation Agency's 

normal operational, repair and maintenance purposes related to the Services. 

ASI shall retain ownership of all Intellectual Property Rights related to Project 

Proprietary Information. 

k. All rights, title and interest in and to, and ownership in, Proprietary Information 

of Implementation Agency, which is provided to ASI, and all modifications, 

enhancements and other derivative works of such Implementation Agency 

Proprietary Information ("Implementation Agency Proprietary Information"), 

shall remain solely with Implementation Agency. The Implementation Agency 

will upon the award of the Project in its favor, declare the status of all the 

Implementation Agency Proprietary Information along with documentary 

support sufficient to establish its sole legal rights in the aforesaid Proprietary 

Information to ASI. This Proprietary Information shall refer to that which has 

been owned by the Implementation Agency prior to commencement of the 

Agreement. Additionally, any software that may be acquired from third parties 



during the term of the agreement and that which may be developed by the 

Implementation Agency during the course of the Agreement specifically for 

Project shall also not be considered as Implementation Agency Proprietary 

Information by the Project. ASI shall be entitled to use such Implementation 

Agency Proprietary Information only in connection with the Services or to the 

extent necessary for Projects oal opeatioal, epai ad aiteae 

purposes related to the Services. To the extent that the Implementation Agency 

Proprietary Information is incorporated within the Deliverables, Implementation 

Agency and its employees engaged hereby grant to ASI a worldwide, perpetual, 

irrevocable, non-exclusive, transferable, paid-up right and license to use, copy, 

modify (or have modified), transport to Project facilities, and prepare from them, 

use and copy derivative works for the benefit of and internal use of Project such 

Implementation Agency Proprietary Information. ASIs ights pusuat to the 

preceding sentence include the right to disclose such Implementation Agency 

Proprietary Information to third party contractors solely for use on Project 

provided that all such third party contractors execute, deliver and comply with 

any customary confidentiality and nondisclosure agreements reasonably 

required by ASI. 

l. With respect to ownership of the Deliverables, the Parties agree that the 

following shall apply: 

(i) All the deliverables provided to ASI by Implementation Agency during the 

course of its performance under this Agreement, and/or the SLA which 

includes but is not limited to e-Ticketing Software as defined in this 

Agreement, in which, subject to the foregoing provisions of this Article, all 

right, title and interest in and to such Deliverables, shall, as between 

Implementation Agency and ASI. To the extent that the Implementation 

Agency Proprietary Information is incorporated within the Deliverables, 

Implementation Agency and its employees engaged hereby grant to ASI a 

worldwide, perpetual, irrevocable, non-exclusive, transferable, paid-up 

right and license to use, copy, modify (or have modified), transport to ASI 

at facilities and locations provided by ASI, and prepare from them, use and 

copy derivative works for the benefit of and internal use of Project, of such 

Implementation Agency Proprietary Information. 

(ii) If Implementation Agency proceeds to apply for, or assign to any third 

party, any patent rights relating to Implementation Agency Proprietary 



Information referred to in the above clause, Implementation Agency will 

ensure that A“Is rights as provided herein are preserved. 

m. ASI hereby grants to Implementation Agency a non-exclusive right and license to 

access and use the Project Proprietary Information solely for the purpose of 

providing Services to ASI. Such right and license shall terminate upon the 

expiration or termination of this Agreement. 

n. Upon the expiration or any termination of this Agreement (and also in respect of 

the SLA), Implementation Agency shall undertake the actions set forth below in 

this Article to assist ASI to procure replacement services equivalent to Services 

provided hereunder. 

(iii) The Implementation Agency undertakes to negotiate in good faith with ASI and 

any relevant Replacement Implementation Agency in respect of commercial terms 

applying to all Implementation Agency Intellectual Property Rights and which ASI 

and any relevant Replacement Implementation Agency require to enable them to 

provide or receive services substantially equivalent to the Services hereunder. 

(iv) In respect of Implementation Agencys usage of thid pat Itelletual Popet 

Rights, Implementation Agency undertakes to assist ASI to secure such consents 

or licenses from such third parties as are necessary to enable Project to receive 

services substantially equivalent to the Services hereunder. The obligations of the 

Implementation Agency under this Article shall be considered part of the services 

5.8. Article VIII – Miscellaneous 

5.8.1. Confidentiality 

b. The Implementation Agency recognizes that during the term of this MSA/ 

Agreement and the SLA, sensitive data will be procured and made available to it, 

its Sub contractors and agents and others working for or under the 

Implementation Agency. Disclosure or usage of the data by any such recipient 

may constitute a breach of applicable laws causing harm to the concerned 

Department. The function of ASI requires the Implementation Agency, its 

Subcontractors and agents to demonstrate utmost care, sensitivity and strict 

confidentiality. Any breach of this Article will result in ASI and its nominees 

receiving a right to seek injunctive relief and damages without any limit, from 

the Implementation Agency and/or also seek termination. 

c. IA agrees as to any Confidential Information disclosed by ASI or the SLA (the 

"Discloser") to this Agreement: 



(i) to take suh steps eessa to potet the A“Is Cofidetial Ifoatio 

from unauthorized use, reproduction and disclosure as the Recipient takes 

in relation to its own Confidential Information of the same type, but in no 

event less than reasonable care; and 

(ii) to use such Confidential Information only for the purposes of this 

Agreement or the SLA or as otherwise expressly permitted or expressly 

required by this Agreement or the SLA or as otherwise permitted by ASI in 

writing; and 

(iii) ot, ithout A“Is pio itte oset, to op the Cofidetial 

Information or cause or allow it to be copied, directly or indirectly, in whole 

or in part, except as otherwise expressly provided in this Agreement or the 

“LA, o as euied i oetio ith IAs use as peitted ude this 

Article, or as needed for the purposes of this Agreement or the SLA, 

provided that any proprietary legends and notices (whether of ASI or of a 

Third Party) are not removed or obscured; and 

(iv) Not, ithout A“Is pio itte oset, to dislose, tasfe, pulish o 

communicate the Confidential Information in any manner to any person 

except as permitted under this Agreement or the SLA. 

d. The restrictions of this Article shall not apply to Confidential Information that: 

(i) is or becomes generally available to the public through no breach of this 

Article by IA; and 

(ii) as i the IAs possessio fee of a oligatio of ofidee pio to the 

time of receipt of it by the IA hereunder; and 

(iii) is deeloped the IA idepedetl of a of A“Is Cofidetial 

Information; and 

(iv) is rightfully obtained by the IA from third parties authorized at that time to 

make such disclosure without restriction; and 

(v) is identified in writing by ASI as no longer proprietary or confidential; or 

(vi) is required to be disclosed by law, regulation or Court Order or under the 

Right to Information Act, or to be furnished to the Parliament and/or its 

Committees, provided that the IA gives prompt written notice to ASI of 

such legal and regulatory requirement to disclose so as to allow the 

Discloser reasonable opportunity to contest such disclosure. 



e. To the extent that such disclosure is required for the purposes of this Agreement 

or the SLA, IA may disclose Confidential Information to: 

(i) its employees, agents and independent contractors and to any of its 

affiliates and their respective independent contractors or employees but all 

of them should in turn be bound to maintain the confidentiality referred to 

herein on their part; and 

(ii) its professional advisors and auditors, who require access for the purposes 

of this Agreement or the SLA, whom the relevant Party has informed of its 

obligations under this Article and in respect of whom the relevant Party has 

used commercially reasonable efforts to ensure that they are contractually 

obliged to keep such Confidential Information confidential on terms 

substantially the same as set forth in this Article. IA may also disclose 

Confidential Information to any entity with A“Is pio itte oset. 

f. The provisions of this Article shall survive the expiration or any earlier 

termination of this Agreement. 

g. Confidential Information shall be and remain the property of ASI and nothing in 

this Article shall be construed to grat IA a ight o liese ith espet to A“Is 

Confidential Information otherwise than as is expressly set out in this 

Agreement. 

h. Subject as otherwise expressly provided in this Agreement all Confidential 

Information in tangible or electronic form under the control of the IA shall either 

be destroyed, erased or returned to ASI promptly upon the earlier of: (i) the 

written request of ASI or, (ii) termination or expiry of this Agreement or, in 

respect of the SLA, the termination or expiry of the SLA. Notwithstanding the 

forgoing, IA may retain, subject to the terms of this Article, a reasonable number 

of opies of A“Is Cofidetial Ifoatio solel fo ofiatio of opliae 

with the confidentiality obligations of this Agreement. 

i. IA is not restricted by the provisions of Article 8.1 from using (including using to 

provide products or perform services on behalf of third parties) any ideas, 

oepts, koho ad tehiues that ae elated to the IAs usiess 

activities and which are retained in unaided eoies of the IAs eploees o 

agents (and not intentionally memorized for the purpose of later recording or 

use) (collectively, the "Residuals"). This Article shall not permit the disclosure or 

use by IA of any financial (including business plans), statistical, product, 



personnel or customer data of ASI. IA agrees not to disclose the source of the 

Residuals. 

j. IA agrees that monetary damages would not be a sufficient remedy for any 

breach of this Article by IA and that ASI shall be entitled to equitable relief, 

including injunction and specific performance as a remedy for any such breach. 

Such remedies shall not be deemed to be the exclusive remedies for a breach by 

IA, but shall be in addition to all other remedies available at law or equity to ASI. 

In connection with the Services, Implementation Agency may from time to time undertake 

one or more quality assessment reviews for the purpose of improving Project. In order for 

such reviews to be frank and candid, for the greatest benefit to ASI and Implementation 

Agency, they shall be kept confidential to the greatest extent possible. The Parties agree 

that any documentation created in connection with such quality assessment reviews shall 

be Confidential Information of Implementation Agency which is licensed to ASI for any 

internal use except that in no event shall such documentation or the results of such reviews 

be discoverable or admissible (or used for any purpose) in any arbitration or legal 

proceedings against Implementation Agency related to this Agreement or the Services. 

k. ASI may permit the Implementation Agency to come into possession of 

confidential public records as per the needs of the project and the 

Implementation Agency shall maintain the highest level of secrecy, 

confidentiality and privacy with regard thereto. 

l. Additionally, the Implementation Agency shall keep confidential all the details 

and information with regard to the Project, including systems, facilities, 

operations, management and maintenance of the systems/ facilities. 

m. Implementation Agency shall be prohibited from using ASI related data in 

whatever manner, for purposes other than handling transactions through ASI 

system. Implementation Agency shall undertake, on behalf of its agents and 

employees, that no ASI related data shall be copied in any manner (paper, 

electronic, or human memory) and transferred to any entity (human or machine) 

other than that being through ASI system for delivering job responsibilities 

defined for each individual. 

n. ASI shall retain all rights to prevent, stop and if required take the necessary 

punitive action against the Implementation Agency regarding any forbidden 

disclosure. 



o. The Implementation Agency shall ensure that all its employees, agents and subcontractors 

execute individual non-disclosure agreements, which have been duly 

approved by ASI, with respect to this Project. 

p. The aforesaid provisions shall not apply to the information: 

(i) already in the public domain; and 

(ii) Disclosed to the public due to a court order or under the Right to Information Act; 

and 

(iii) Information required to be furnished to the Parliament and/or its Committees 

5.8.2. Personnel 

a. Personnel assigned by Implementation Agency to perform the Services shall be 

employees of Implementation Agency and of the sub-contracting agency, and 

under no circumstances will such personnel be considered employees of the 

Project. Implementation Agency and of the sub-contracting agency shall have 

the sole responsibility for supervision and control of its personnel and for 

payment of such personnel's entire compensation, including salary, withholding 

of income taxes and social security taxes, worker's compensation, employee and 

disability benefits and the like and shall be responsible for all employer 

obligations under all applicable laws. 

b. Implementation Agency shall ensure that sufficient Implementation Agency 

personnel are employed to perform the Services, and also that such personnel 

have appropriate qualifications to perform the Services. ASI shall have the right 

to require the removal or replacement of any Implementation Agency personnel 

performing work under this Agreement. In the event that ASI requests that any 

Implementation Agency personnel be replaced, the substitution of such 

personnel shall be accomplished pursuant to a mutually agreed upon schedule 

but not later than 3 working days. 

c. The Implementation Agency shall also be responsible to train certain employees 

of Project with regard to the Services being provided by the Implementation 

Agency as and when required by Project during the Term of this Project. The 

parameters of the training required for these employees of Project shall be 

communicated by ASI to the Implementation Agency periodically and shall be in 

accordance with the latest procedures and processes available in the relevant 

areas of work. 



d. In the event, ASI identifies any personnel of Implementation Agency as "Key 

Personnel", then the Implementation Agency shall not remove such personnel 

without the prior written consent of ASI under the applicable terms of this 

Agreement and/or SLA. 

e. Except as stated in this Article, nothing in this Agreement or the SLA will limit the 

ability of Implementation Agency or any Implementation Agency freely to assign 

or reassign its employees; provided that Implementation Agency shall be 

responsible, at its expense, for transferring all appropriate knowledge from 

personnel being replaced to their replacements. ASI shall have the right to 

review and approve Implementation Agency's plan for any such knowledge 

transfer. Implementation Agency shall maintain the same standards for skills and 

professionalism among replacement personnel as in personnel being replaced. 

f. Each Party shall be responsible for the performance of all its obligations under 

this Agreement or the SLA and shall be liable for the acts and omissions of its 

employees and agents in connection therewith. 

5.8.3. Independent Contractor 

Nothing in this Agreement or the SLA shall be construed as establishing or implying 

any agency or joint venture between the Parties to this Agreement or the SLA and, 

except as expressly stated in this Agreement or the SLA, nothing in this Agreement 

or the SLA shall be deemed to constitute any Parties as the agent of any other 

Party or authorizes either Party (i) to incur any expenses on behalf of the other 

Party, (ii) to enter into any engagement or make any representation or warranty on 

behalf of the other Party, (iii) to pledge the credit of or otherwise bind or oblige the 

other Party, or (iv) to commit the other Party in any way whatsoever without in 

each case obtaining the other Party's prior written consent. 

5.8.4. Sub-Contractors 

Implementation Agency shall not subcontract any work related to the following 

works related to the implementation of Project to be performed under this 

Agreement without ASI 's prior written consent. It is clarified that the IA shall be 

the principal employer for all claims arising from the liabilities statutory or 

otherwise, concerning the subcontractors. IA undertakes to indemnify ASI or its 

nominated agencies from any claims on the grounds stated hereinabove. 

(a) Design, Development and Installation of e-Ticketing Application Software 



(b) Installation and Management of e-Ticketing system Infrastructure 

(c) Operation and Maintenance of software applications and IT Infrastructure 

relating to ASI 

(d) The bidder shall not sub-contract the work relating to the customization and 

design of the e-Ticketing Solution (ETS) application and application 

deployment at DC and DRC. 

(e) However, any other sub-contractors may be hired by the Implementation 

Agency where the Implementation Agency shall be the principal employer for 

all claims arising from the liabilities statutory or otherwise, concerning the 

sub-contractors. The Implementation Agency undertakes to indemnify ASI or 

its nominated agencies from any claims on the grounds stated herein above. 

Prospective subcontractor Statement 

a) Bidder shall identify all prospective subcontractors, if any, which the bidder 

will engage, to provide the services required under this RFP. For each 

proposed subcontractor, bidder shall provide the following: 

b) Brief description of nature of products/services to be provided by 

subcontractor; 

c) Head and branch offices (if responsible for work under this contract) (provide 

street and mailing addresses, phone, fax and email); 

d) Date, form and state of incorporation; 

e) Contract administrator (Name, business address, fax, phone and email 

address of individual responsible for administering any contract that might 

result from this RFP); 

f) Company principals (Name, title and business address); and, 

g) Current or prior successful partnerships with proposed subcontractor 

including client reference (Contact Name, Phone Number, dates when 

services were performed). 

5.8.5. Assignment 

All terms and provisions of this Agreement shall be binding on and shall inure to the 

benefit of ASI and Implementation Agency and any assignment or transfer of this 



Agreement or the SLA or any rights hereunder by the Implementation Agency shall be 

strictly prohibited. 

5.8.6. Trademarks, Publicity 

Neither Party may use the trademarks of the other Party without the prior written 

consent of the other Party. Except as required by law or the rules and regulations of 

each stock exchange upon which the securities of one of the Parties is listed, neither 

Party shall publish or permit to be published either along with or in conjunction with any 

other person any press release, information, article, photograph, illustration or any 

other material of whatever kind relating to this Agreement, the SLA or the business of 

the Parties without prior reference to and approval in writing from the other Party. . 

5.8.7. Notices 

a. Any notice or other document, which may be given by either Party under this 

MSA/Agreement or under the SLA, shall be given in writing in person or by pre-paid 

recorded delivery post or by facsimile transmission. 

b. In relation to a notice given under this Agreement, any such notice or other 

document shall be addressed to the other Party's principal or registered office 

address as set out below: 

Archeological Survey of India 

Addess: ………………. 

Tel: ……………………… 

Fa: ……………………… 

Eail:……………………. 

Implementation Agency: 

Addess: ………………. 

Tel:……………………… 

Fa:……………………… 

Eail:……………………… 

c. Any notice or other document shall be deemed to have been given to the other 

Party (or, if relevant, its relevant associated company) when delivered (if delivered 

in person) if delivered between the hours of 9.00 am and 5.30 pm on a working day 



at the address of the other Party set forth above or if sent by fax, provided the copy 

fax is accompanied by a confirmation of transmission, or on the next working day 

thereafter if delivered outside such hours, and 7 days from the date of posting (if by 

letter). 

d. Either Party to this Agreement or to the SLA may change its address, telephone 

number, facsimile number and nominated email for notification purposes by giving 

the other reasonable prior written notice of the new information and its effective 

date. 

5.8.8. Variations And Further Assurance 

a. No amendment, variation or other change to this Agreement or the SLA shall be 

valid unless authorized in accordance with the change control procedure as set out 

in the Change Control Schedule and made in writing and signed by the duly 

authorized representatives of the Parties to this Agreement or the SLA. 

b. Each Party to this Agreement or the SLA agrees to enter into or execute, without 

limitation, whatever other agreement, document, consent and waiver and to do all 

other things which shall or may be reasonably required to complete and deliver the 

obligations set out in this Agreement or the SLA. 

5.8.9. Severability And Waiver 

a. If any provision of this Agreement or the SLA, or any part thereof, shall be found by 

any court or administrative body of competent jurisdiction to be illegal, invalid or 

unenforceable the illegality, invalidity or unenforceability of such provision or part 

provision shall not affect the other provisions of this Agreement or the SLA or the 

remainder of the provisions in question which shall remain in full force and effect. 

The relevant Parties shall negotiate in good faith in order to agree to substitute for 

any illegal, invalid or unenforceable provision a valid and enforceable provision 

which achieves to the greatest extent possible the economic, legal and commercial 

objectives of the illegal, invalid or unenforceable provision or part provision. 

b. No failure to exercise or enforce and no delay in exercising or enforcing on the part 

of either Party to this Agreement or the SLA of any right, remedy or provision of this 

Agreement or the SLA shall operate as a waiver of such right, remedy or provision in 

any future application nor shall any single or partial exercise or enforcement of any 

right, remedy or provision preclude any other or further exercise or enforcement of 

such right, remedy or provision or the exercise or enforcement of any other right, 

remedy or provision. 



5.8.10. Compliance With Laws And Regulations 

Each Party to this Agreement and the SLA accepts that its individual conduct shall 

(to the extent applicable to it) at all times comply with all applicable laws, rules and 

regulations. For the avoidance of doubt, the obligations of the Parties to this 

Agreement and the SLA are subject to their respective compliance with all 

applicable laws and regulations. 

5.8.11. Ethics 

Implementation Agency represents, warrants and covenants that it has given no 

commitments, payments, gifts, kickbacks, lavish or expensive entertainment, or 

other things of value to any employee or agent of ASI, or its nominated agencies in 

connection with this agreement and acknowledges that the giving of any such 

payment, gifts, entertainment, or other things of value is strictly in violation of 

A“Is stadad poliies ad a esult i aellatio of this Ageeent, and the 

SLA. 

5.8.12. Entire Agreement 

This Agreement, and the SLA, all schedules appended thereto and the contents and 

specifications of all the Volumes of the RFP constitute the entire agreement 

between the Parties with respect to their subject matter, and as to all other 

representations, understandings or agreements which are not fully expressed 

herein. 

5.8.13. Survivability 

The termination or expiry of this Agreement or the SLA for any reason shall not 

affect or prejudice any terms of this Agreement, or the rights of the Parties under 

them which are either expressly or by implication intended to come into effect or 

continue in effect after such expiry or termination. 

5.8.14. Force Majeure 

a. Neither Party to this Agreement or to the SLA shall be liable to the other for any 

loss or damage which may be suffered by the other due directly to the extent 

and for the duration of any cause beyond the reasonable control of the Party 

unable to perform ("Force Majeure") events such as but not limited to acts of 

God not confined to the premises of the Party claiming the Force Majeure, flood, 

drought, lightning, fire caused by natural forces, earthquakes, strike, lock-outs 



beyond its control, Labour disturbance not caused at the instance of the Party 

claiming Force Majeure, Acts of government or other competent authority, war, 

terrorist activities, military operations, riots, epidemics, civil commotions etc. No 

failure, delay or other default of any contractor or sub-contractor to either Party 

shall entitle such Party to claim Force Majeure under this Article. 

b. The Party seeking to rely on Force Majeure shall promptly, within 2 days, notify 

the other Party of the occurrence of a Force Majeure event as a condition 

precedent to the availability of this defense with particulars detailed in writing to 

the other Party and shall demonstrate that it has taken and is taking all 

reasonable measures to mitigate the events of Force Majeure. 

c. In the event the Force Majeure substantially prevents, hinders or delays the 

Implementation Agency's performance of Seies eessa fo Pojets 

ipleetatio o the opeatio of Pojets itial usiess futios fo a 

period in excess of 5 days, ASI may declare that an emergency exists. However, 

when the situation arising out of force majeure comes to an end in the 

assessment of ASI the following conditions shall apply: 

Prior to commencement of operations: If the event of Force Majeure had occurred prior 

to commencement of operations, upon its coming to an end the Implementation Agency 

shall resume normal activities under this Agreement immediately. ASI if considers it 

necessary, may grant an extension of time to the Implementation Agency for resuming 

normal activities under this Agreement. If the Implementation Agency does not resume 

normal activities immediately or within the extended period, if any, granted by ASI, ASI 

will have the option to invoke the Performance Guarantee, levy liquidated damages as per 

clause 4.4 of this Agreement, obtain substitute performance from an alternate supplier at 

the cost of Implementation Agency and/or terminate this Agreement. 

Post commencement of operations: If Force Majeure had occurred post commencement 

of operations, upon its coming to an end, the Implementation Agency shall resume 

normal services under this agreement immediately. ASI if considers it necessary, may 

grant an extension of time to the Implementation Agency for resuming normal services 

under this agreement. However, ASI will deduct for each day of the extension period a 

percentage proportionate to the number of days and the volume(s) (measured in terms of 

ratio to the overall volume as recorded in the previous month) expected in the affected 

area(s) from the next payable amount as per Payment Schedule. If normal services are not 

resumed immediately or within the extended time, ASI will have the option to invoke the 

Performance Guarantee and/or terminate the Agreement. 



d. All payments pursuant to termination due to Force Majeure event shall be in 

accordance with the Terms of Payment Schedule (Schedule VI of this 

Agreement). 

e. Notwithstanding the terms of this Article, the failure on the part of the 

Implementation Agency under the SLA or terms under the SLA to implement any 

disaster contingency planning and back-up and other data safeguards in 

accordance with the terms of the SLA or this Agreement against natural disaster, 

fire, sabotage or other similar occurrence shall not be an event of Force Majeure. 

5.9. Article IX - Disputes 

5.9.1. Dispute Resolution 

Any dispute arising out of or in connection with this Agreement or the SLA shall 

in the first instance be dealt with in accordance with the escalation procedure as 

set out in the Governance Schedule (Schedule IV of this Agreement). 

Any dispute or difference whatsoever arising between the Parties to this 

Agreement out of or relating to the construction, meaning, scope, operation or 

effect of this Agreement or the validity of the breach thereof, which cannot be 

resolved through the application of the provisions of the Governance Schedule, 

shall be dealt in accordance with the provisions set forth herein. 

a. Scope of Dispute Resolution 

Except where otherwise provided in the agreement, all questions and disputes 

relating to the meaning of the specifications, design, drawings and instructions 

here-in before mentioned and as to the quality of workmanship or materials 

used on the work or as to any other question, claim, right, matter or thing 

whatsoever in any way arising out of or relating to the agreement, designs, 

drawings, specifications, estimates, instructions, orders or these conditions or 

otherwise concerning the services and deliverables or the execution or failure to 

execute the same whether arising during the progress of the Project or after the 

cancellation, termination, completion or abandonment thereof shall be dealt 

with as mentioned hereinafter: 

b. Dispute Resolution Board 

If any dispute arises between ASI and the Implementation Agency in connection 

with, or arising out of, the agreement or the execution of the Project, whether 



during the execution of the Project or after its completion and whether before or 

after the repudiation or other termination of the agreement, including any 

disagreement by either party with any action, inaction, opinion, instruction, 

determination, certificate or valuation, the matter in dispute shall, in the first 

place, be referred to the Dispute Resolutio Boad hee i afte alled the 

Boad. 

For purposes of this agreement, the Operations Committee referred to under 

section 3.1 of Volume III of the RFP, shall act as the Board. The board at its 

discretion may co-opt any other officer if in its opinion it may help in resolving 

the dispute. Either party may refer a dispute to the Board. The board shall give a 

decision in writing within 30 days of reference of dispute. Either party may refer 

a written decision of the board to arbitration. If neither party refers the disputes 

to aitatio ithi das of the date of suh deisio, the Boads deisio 

will be final and binding. 

ASI at its discretion may change any of the members of the board. 

c. Arbitration 

a) In the event of any dispute or difference between the parties hereto, such 

disputes or differences shall be resolved amicably by mutual consultation. If such 

resolution is not possible, then unresolved dispute or difference shall be referred 

to the arbitrator to be appointed by ASI, Government of India on the 

eoedatio of the “eeta, Depatet of Legal Affais La “eeta, 

Government of India. The provisions of Arbitration & Conciliation Act, 1996 

(No.26 of 1996) shall be applicable to the Arbitration. The venue of such 

arbitration shall be at Delhi or any other place, as may be decided by arbitrator. 

The language of arbitration proceedings shall be English. The arbitrator shall 

ake a easoed aad the Aad, hih shall e fial ad iding on the 

parties. The cost of arbitration shall be shared equally by the parties to the MSA. 

However, expenses occurred by each party in connection with preparation, 

presentation should be borne by the parties itself. 

b) Pending the submission of and/or decision on dispute, differences of claim or 

until the arbitral award is published; the parties shall continue to perform all of 

their obligations under this contract without prejudice through a final 

adjustment in accordance with such award. 



c) The parties agree that any decision for Award of any Arbitral Tribunal pursuant 

to this clause shall be a domestic award and final, conclusive and binding upon 

the parties and any person affected by it. The parties also agree that any 

arbitration award rendered pursuant to this clause may be enforced by any court 

of competent jurisdiction. 

d) During any period of arbitration, there shall be no suspension of this Agreement. 

e) The parties specifically agree that any arbitration shall be pursuant to clause 

above. 

f) This clause is governed by Indian Law. 

5.10. Article X - Amendment 

The Parties acknowledge and agree that amendments to this Agreement shall be made 

through mutual agreement between the parties in writing in accordance with the 

procedure this Agreement is executed and signed. 

IN WITNESS WHEREOF the Parties have by duly authorized representatives set their 

respective hands and seal on the date first above written in the presence of: 

WITNESSES: 

1. (Name, Designation, Organization, and Signature) 

2. (Name, Designation, Organization, and Signature) 

Archeological Survey of India [IMPLEMENTATION AGENCY] 

Signed Signed 

For and on behalf of the For and on behalf of the 

President of India _______ (Company name) _______ 

By: ____ (signature) ______ By: ____ (signature) ______ 

___ (Name and designation) ____ ____ (Name and designation) ___ 

An authorized signatory duly nominated pursuant 

to Board Resolution No._______ dated_______ of 

the [Implementation Agency] 



6. SCHEDULE I 

CHANGE CONTROL SCHEDULE 

6.1. Purpose 

This Schedule applies to and describes the procedure to be followed in the event of any 

poposed hage to the Maste “eies Ageeet M“A, Pojet Ipleetatio 

Phase, and Operation and Management SLA. Such change shall include, but shall not be 

limited to, changes in the scope of services provided by the Implementation Agency and 

changes to the terms of payment as stated in the Terms of Payment Schedule (Schedule VI 

of this Agreement). 

ASI and the Implementation Agency recognize that frequent change is an inevitable part of 

delivering services and that a significant element of this change can be accomplished by reorganizing 

processes and responsibilities without a material effect on the cost. The 

Implementation Agency will endeavor to the best of its ability and in accordance with 

prevailing market practices, to effect change without an increase in the terms of payment 

as stated in the Terms of Payment Schedule and ASI will work with the Implementation 

Agency to ensure that all changes are discussed and managed in a constructive manner. 

6.2. Change Control Note ("CCN") 

a. Change requests in respect of the MSA, the Project Implementation, or the Operation 

and Management SLA will emanate from the Parties' respective Project Manager who 

will be responsible for obtaining approval for the change and who will act as its sponsor 

throughout the Change Control Process and will complete Part A of the CCN attached as 

Schedule VII hereto. CCNs will be presented to the other Party's Project Manager who 

will acknowledge receipt by signature on the CCN. 

b. The Implementation Agency and ASI while preparing the CCN, shall consider the change 

in the context of the following parameter, namely whether the change is beyond the 

scope of Services including ancillary and concomitant services required and as detailed 

in Volume I of the RFP and is suggested and applicable only after the testing, 

commissioning and certification of the Pilot Phase and the Project Implementation 

Phase as set out in this Agreement. 

c. It is hereby also clarified that the payment for the changes brought in after project 

etifiatio ad Fial Go Lie date ill e alulated o the asis of leded amonth 

rate quoted by the Implementation Agency in its bid and estimated man-month 



effort to be submitted by the Implementation Agency prior to taking up the change of 

control event and accepted by ASI. 

d. Cumulative value of all change requests will be limited to 10 % of the value of this 


6.3. Quotation 

i. The Implementation Agency shall assess the CCN and complete Part B of the CCN. In 

completing Part B of the CCN the Implementation Agency shall provide as a 

minimum: a description of the change which should also provide Name of 

functionality/feature being changed, current functionality/feature (prior to change), 

new functionality/feature (post change); 

ii. a list of deliverables required for implementing the change; 

iii. a timetable for implementation; 

iv. an estimate of the timelines or effort of any proposed change; 

v. the unit of measure to cost the change; 

vi. an estimate of any proposed change; 

vii. any relevant acceptance criteria; 

viii. an assessment of the value of the proposed change; 

ix. Material evidence to prove that the proposed change is not already covered within 

the scope of the Project, SLA, or MSA. 

x. Description of the circumstances which influenced the origin of this change. 

xi. Alternative options possible to address the change if any and the implications of 

these alternative options. 

xii. Detailed break up of various categories of activities to be performed for 

implementing a proposed change along with details on where re-usable components 

are used to reduce the efforts. 

xiii. Details on software change estimation method used for the calculation of change 

effort estimation to provide information on how change is classified in various 

categories, what all items that require efforts and how efforts are estimated. 

xiv. Underlying Assumptions. 



xv. Any other details that ASI would require to assess the effort estimated provided by the 

Implementation Agency. 

a. Prior to submission of the completed CCN to ASI or its nominated agencies, the 

Implementation Agency will undertake its own internal review of the proposal and obtain 

all necessary internal approvals. As a part of this internal review process, the 

Implementation Agency shall consider the materiality of the proposed change in the context 

of the MSA, the Project Implementation, Operation and Management SLA affected by the 

change and the total effect that may arise from implementation of the change. 

b. Materiality criteria will be established by ASI and the Implementation Agency's Project 

Manager. Changes requiring no escalation of authority can be implemented. Discussion and 

agreement as to materiality will be held in accordance with the Governance Schedule 

(Schedule IV of this Agreement). 

6.4. Costs 

Each Party shall be responsible for its own costs incurred in the quotation, preparation of 

CCNs and in the completion of its obligations described in this process provided the 

Implementation Agency meets the obligations as set in the CCN. In the event the 

Implementation Agency is unable to meet the obligations as defined in the CCN then the 

cost of getting it done by third party will be borne by the Implementation Agency. 

6.5. Reporting 

Change requests and CCNs will be reported monthly to each Party's Project Managers who 

will prioritize and review progress. 

6.6. Obligations 

The Implementation Agency shall be obliged to implement any proposed changes once 

approval in accordance with above provisions has been given, with effect from the date 

agreed for implementation and within an agreed timeframe. 



7. SCHEDULE II 

EXIT MANAGEMENT SCHEDULE 

7.1. Purpose 

a. This Schedule sets out the provisions, which will apply prior to the expiry of the Agreement 

or termination of the MSA, the Project Implementation, Operation and Management SLA is 

initiated. 

b. It sets out the provisions which will ensure that ASI will be able to offer the services to its 

Stakeholders without any interruptions on expiry or termination of the Agreement. 

c. Continuity and performance of the Services at all times including the duration of the Agreement and 

post expiry of the Agreement is a critical requirement of ASI. It is the prime responsibility of 

Implementation Agency to ensure continuity of service at all times of the Agreement including exit 

management period and in no way any facility/service shall be affected/degraded. Further, 

Implementation Agency is also responsible for all activities required to train and transfer the 

knowledge to the Replacement Implementation Agency to ensure similar continuity and 

performance of the Services post expiry of the Agreement. Implementation Agency will be required 

to carry out a gap analysis of the facilities and arrangements made by the Replacement 

Implementation Agency and specifically inform ASI. It sets out the mechanisms for Exit Management 

Services the Service Provider is to provide on termination or prior to expiration of the Agreement to 

allow the orderly and efficient transition of the Services to ASI or its nominee. 

d. It sets out the mechanisms for managing the knowledge enablement services the Service Provider 

has to provide to allow ASI to create an understanding of the operations and technology of the 

systems for itself or its nominees or any designated agencies. 

e. The Parties shall ensure that their respective associated entities carry out their respective 

obligations set out in this Exit Management Schedule. 

7.2. Transfer Of Assets 

a. All assets procured by IA shall be owned by ASI. ASI shall be entitled to serve notice in 

writing on the Implementation Agency at any time during the exit management period as 

detailed herein above requiring the Implementation Agency and/or its sub-contractors to 

provide ASI with a complete and upto date list of the Assets within 30 days of such notice. 

ASI shall then be entitled to serve notice in writing on the Implementation Agency at any 

time prior to the date that is 30 days prior to the end of the exit management period 

requiring the Implementation Agency to transfer all the Assets to ASI. 



b. In case of Agreement being terminated by ASI, ASI reserves the right to ask IA to continue 

running the Project operations for a period of 6 months after termination orders are issued. 

Such period can be extended if the transfer is not complete and/or not done to the 

satisfaction of ASI. In case of successful transfer to the satisfaction of ASI is achieved before 

the period of 6 months after termination orders, ASI reserves the right to relieve IA of the 

obligation to run Project operations earlier than the period of 6 months. 

c. Upon service of a notice under this Article the following provisions shall apply: 

(i) All risk and titles to the Assets to be transferred to ASI, ASI pursuant to this Article 

shall be transferred to Project, on the day of delivery to ASI. 

(ii) ASI shall take over the physical assets from the Implementation Agency on the last 

day of the exit management period. 

(iii) Payment to the outgoing IA shall be made to the tune of last set of completed 

transactions, subject to SLA requirements and for any Capex component that has 

been accepted by ASI but is pending for payment. 

(iv) The outgoing IA will pass on to ASI and/or to the Replacement IA, the subsisting 

rights in any leased properties/ licensed products on terms not less favorable to ASI 

/ Replacement IA, than that enjoyed by the outgoing IA. 

(v) The task of IA with reference to the Exit Management is deemed to be complete 

only when ASI issues a satisfactory completion certificate for the Exit Management. 

7.3. Cooperation And Provision Of Information 

During the exit management period: 

a. the Implementation Agency will allow ASI access to information reasonably required 

to define the then current mode of operation associated with the provision of the 

services to enable ASI to assess the existing services being delivered; 

b. promptly on request by ASI, the Implementation Agency shall provide access to and 

copies of all information held or controlled by them which they have prepared or 

maintained in accordance with the MSA, the Project Implementation, and the 

Operation and Management SLA relating to any material aspect of the Services 

(whether provided by the Implementation Agency or sub-contractors appointed by 

the Implementation Agency). ASI shall be entitled to copy all such information. Such 

information shall include details pertaining to the services rendered and other 

performance data. The Implementation Agency shall permit ASI and/or any 



Replacement Implementation Agency to have reasonable access to its employees 

and facilities as required by ASI to understand the methods of delivery of the 

services employed by the Implementation Agency and to assist appropriate 

knowledge transfer. 

7.4. Confidential Information, Security And Data 

a. The Implementation Agency will promptly on the commencement of the exit 

management period supply to ASI the following: 

(i) information relating to the current services rendered and performance data relating 

to the performance of sub-contractors in relation to the services; 

(ii) douetatio elatig to Pojets Itelletual Popet ‘ights; 

(iii) Project data and confidential information; 

(iv) documentation relating to sub-contractors; 

(v) all current and updated Project data as is reasonably required for purposes of Project 

or its nominated agencies transitioning the services to its Replacement 

Implementation Agency in a readily available format specified by ASI; 

(vi) all other information (including but not limited to documents, records and 

agreements) relating to the services reasonably necessary to enable Project or its 

nominated agencies, or its Replacement Implementation Agency to carry out due 

diligence in order to transition the provision of the Services to Project or its 

nominated agencies, or its Replacement Implementation Agency (as the case may 

be). 

b. Before the expiry of the exit management period, the Implementation Agency shall 

deliver to ASI all new or up-dated materials from the categories set out in Article 

above and shall not retain any copies thereof. 

c. Before the expiry of the exit management period, unless otherwise provided under 

the MSA, ASI shall deliver to the Implementation Agency all forms of 

Implementation Agency confidential information, which is in the possession or 

control of Project or its users. 

7.5. Employees 

a. Promptly on request at any time during the exit management period, the 

Implementation Agency shall, subject to applicable laws, restraints and regulations 

(including in particular those relating to privacy) provide to ASI a list of all employees 



(with job titles) of the Implementation Agency dedicated to providing the services at 

the commencement of the exit management period; 

b. To the extent that any Transfer Regulation does not apply to any employee of the 

Implementation Agency, Project, or its Replacement Implementation Agency may 

make an offer of employment or contract for services to such employee of the 

Implementation Agency and the Implementation Agency shall not enforce or impose 

any contractual provision that would prevent any such employee from being hired 

by ASI or any Replacement Implementation Agency. 

c. ASI or Replacement IA designated by it shall retain the right for hiring a minimum of 

5 key personnel of the outgoing IA spearheading the Project, as identified by ASI, as 

well as an appropriate number of support personnel deployed by the outgoing IA, so 

as to provide for continuity. IA is hence required to incorporate suitable provisions/ 

conditions in the appointment orders issued to its personnel, including a service 

bond to this effect. 

7.6. Transfer Of Certain Agreements 

On request by ASI, the Implementation Agency shall effect such assignments, transfers, 

licenses and sub-licenses as ASI may require in favor of ASI, or its Replacement 

Implementation Agency in relation to any equipment, lease, maintenance or service 

provision agreement between Implementation Agency and third party lessors, 

vendors, and which are related to the services and reasonably necessary for the 

carrying out of replacement services by ASI or its Replacement Implementation 

Agency. 

7.7. Rights Of Access To Premises 

a. At any time during the exit management period, where Assets are located at the 

Implementation Agency's premises, the Implementation Agency will be obliged to 

give reasonable rights of access to (or, in the case of Assets located on a third party's 

premises, procure reasonable rights of access to) ASI and/or any Replacement 

Implementation Agency in order to make an inventory of the Assets. 

b. The Implementation Agency shall also give ASI or its nominated agencies, or any 

Replacement Implementation Agency right of reasonable access to the 

Implementation Agency's premises and shall procure for ASI or its nominated 

agencies and any Replacement Implementation Agency rights of access to relevant 

third party premises during the exit management period and for such period of time 



following termination or expiry of the MSA as is reasonably necessary to migrate the 

services to ASI or its nominated agencies, or a Replacement Implementation Agency. 

7.8. General Obligations Of The Implementation Agency 

a. The Implementation Agency shall provide all such information as may be necessary 

to effect as seamless a handover as practicable in the circumstances to ASI or its 

nominated agencies or its Replacement Implementation Agency and which the 

Implementation Agency has in its possession or control at any time during the exit 

management period. 

b. For the purposes of this Schedule, anything in the possession or control of any 

Implementation Agency, associated entity, or sub-contractor is deemed to be in the 

possession or control of the Implementation Agency. 

c. The Implementation Agency shall commit adequate resources to comply with its 

obligations under this Exit Management Schedule. 

7.9. Exit Management Plan 

a. An Exit Management Plan shall be furnished by Implementation Agency in writing to 

ASI or its nominated agencies within 90 days from the Effective Date of this 

Agreement, which shall deal with at least the following aspects of exit management 

in relation to the MSA as a whole and in relation to the Project Implementation, and 

the Operation and Management SLA. 

(i) A detailed program of the transfer process that could be used in conjunction 

with a Replacement Implementation Agency including details of the means to 

be used to ensure continuing provision of the services throughout the transfer 

process or until the cessation of the services and of the management 

structure to be used during the transfer; 

(ii) plans for the communication with such of the Implementation Agency's subcontractors, 

staff, suppliers, customers and any related third party as are 

eessa to aoid a ateial detietal ipat o Pojets opeations as 

a result of undertaking the transfer; 

(iii) (if applicable) proposed arrangements for the segregation of the 

Implementation Agency's networks from the networks employed by Project 

and identification of specific security tasks necessary at termination; 



(iv) Plans for provision of contingent support to Project and Replacement 

Implementation Agency for a reasonable period after transfer. 

b. The Implementation Agency shall re-draft the Exit Management Plan annually 

thereafter to ensure that it is kept relevant and up to date. 

c. Each Exit Management Plan shall be presented by the Implementation Agency to 

and approved by ASI or its nominated agencies. 

d. The terms of payment as stated in the Terms of Payment Schedule include the costs 

of the Implementation Agency complying with its obligations under this Schedule. 

e. In the event of termination or expiry of MSA, Project Implementation, or Operation 

and Management SLA, each Party shall comply with the Exit Management Plan. 

f. During the exit management period, the Implementation Agency shall continue to 

deliver the Services. 

g. Payments during the Exit Management period shall be made in accordance with the 

Terms of Payment Schedule. 



8. SCHEDULE III 

AUDIT, ACCESS AND REPORTING SCHEDULE 

8.1. Purpose 

This Schedule details the audit, access and reporting rights of ASI and the respective 

obligations of Implementation Agency under the MSA, Project Implementation, Operation 

and Management SLA. ASI shall engage a suitable, neutral and technically competent third 

party agency or agencies for conducting audit and certification, upon intimation by the IA 

that the system implementation is complete. The system shall be audited through a CERTin 

enrolled audit agency. 

The IA being notified of any deviations from the agencies nominated by ASI regarding 

deviations from norms, standards or guidelines shall at the earliest instance, take all 

corrective measures required in least possible time. 

8.2. Audit Notice And Timing 

a. As soon as reasonably practicable after the Effective Date, the Parties shall use their 

best endeavors to agree to a timetable for routine audits during the Project 

Implementation Phase and the Operation and Management Phase. Such timetable may 

be reviewed every 3 months on the sole discretion of ASI. During the Implementation 

Phase, ASI and thereafter during the Operation Management Phase, ASI shall conduct 

routine audits in accordance with such agreed timetable and shall not be required to 

give the Implementation Agency any further notice of carrying out such audits. 

b. ASI may conduct non-timetabled audits at his/ her own discretion if he/ she reasonably 

believes that such non-timetabled audits are necessary as a result of an act of fraud by 

the Implementation Agency, a security violation, or breach of confidentiality obligations 

by the Implementation Agency, provided that the requirement for such an audit is 

notified in writing to the Implementation Agency a reasonable period time prior to the 

audit (taking into account the circumstances giving rise to the reasonable belief) stating 

in a reasonable level of detail the reasons for the requirement and the alleged facts on 

which the requirement is based. If the Implementation Agency considers that the nontimetabled 

audit was not appropriate, the matter shall be referred to the escalation 

procedure as set out in the Governance Schedule (Schedule IV of this Agreement). 

c. The frequency of audits shall be 6 monthly, or as decided by ASI, provided always that 

ASI shall endeavor to conduct such audits with the lowest levels of inconvenience and 

disturbance practicable being caused to the Implementation Agency. 



d. In addition to the above, there will be audits conducted by statutory bodies (e.g. CAG) 

as and when they are required to do it. Notwithstanding any condition given in the 

MSA, Implementation Agency will have to provide these statutory bodies access to all 

the facilities, infrastructure, documents and artifacts of the Project as required by them 

and approved by ASI, in writing. 

e. The audit and access rights contained shall survive the termination or expiration of the 

Agreement. 

8.3. Access 

The Implementation Agency shall provide ASI access to employees, subcontractors, 

suppliers, agents and third party facilities, documents, records and systems reasonably 

required for audit and shall provide all such persons with routine assistance in 

connection with the audits and inspections. ASI shall have the right to copy and retain 

copies of any relevant records. The Implementation Agency shall co-operate with ASI in 

effecting the audits. 

8.4. Audit Rights 

a. ASI shall have the right to audit and inspect suppliers, agents and third party facilities, 

including leased premises for providing Services, data center, data recovery centres, 

documents, records, procedures and systems relating to the provision of the services, 

but only to the extent that they relate to the provision of the services, as shall be 

reasonably necessary to verify: 

(i) The security, integrity and availability of all Project data processed, held or conveyed by 

the Implementation Agency on behalf of Project and documentation related thereto; 

(ii) That the actual level of performance of the services is the same as specified in the SLA; 

(iii) That the Implementation Agency has complied with the relevant technical standards, 

and has adequate internal controls in place; and 

(iv) The compliance of the Implementation Agency with any other obligation under the MSA 

and SLA. 

8.5. Audit Rights Of Sub-Contractors, Suppliers And Agents 

a. The Implementation Agency shall perform the same audit and access provisions as 

defined in this Schedule with sub-contractors, suppliers and agents who supply 

labor, services, equipment or materials in respect of the services. The 

Implementation Agency shall inform ASI prior to concluding any sub-contract or 

supply agreement of any failure to achieve the same rights of audit or access. 



REPORTING: The Implementation Agency will provide monthly reports to ASI regarding any specific 

aspects of the Project and in context of the audit and access information as required by ASI. 

8.6. Action And Review 

a. Any change or amendment to the systems and procedures of the Implementation 

Agency, or sub-contractors, where applicable, arising from the audit report shall be 

agreed within thirty (30) calendar days from the submission of the said report. 

b. Any discrepancies identified by any audit pursuant to this Schedule shall be 

immediately notified to ASI or the appropriate Project Manager and the 

Implementation Agency Project Manager who shall determine what action should 

be taken in respect of such discrepancies in accordance with the terms of the MSA. 

8.7. Terms Of Payment For Cost Of Audit 

ASI and the Implementation Agency and its sub-contractors, if any, shall bear their own 

costs of any audits and inspections. The terms of payment are inclusive of any costs of the 

Implementation Agency and the sub-contractor, for all reasonable assistance and 

information provided under the MSA, the Project Implementation, Operation and 

Management SLA by the Implementation Agency pursuant to this Schedule. 

8.8. Records And Information 

For the purposes of audit in accordance with this Schedule, the Implementation Agency 

shall maintain true and accurate records in connection with the provision of the services 

and the Implementation Agency shall handover all the relevant records and documents 

upon the termination or expiry of the MSA. 



9. SCHEDULE IV 

GOVERNANCE SCHEDULE 

9.1. Purpose 

.1 The purpose of this Schedule is to (i) establish and maintain the formal and informal 

processes for managing the relationship between ASI and the Implementation Agency 

(including the outputs from other Schedules to this Agreement; (ii) define the principles 

that both Parties wish to follow to ensure the delivery of the Services; (iii) ensure the 

continued alignment of the interests of the Parties; (iv) ensure that the relationship is 

maintained at the correct level within each Party; (v) create the flexibility to revise and 

maintain the relationship and this Agreement during the Term; (vi) set out the procedure 

for escalating disagreements; and (vii) enable contract administration and performance 

management. 

9.2. Governance Structure 

a. The Program Governance Structure to be put in place by ASI will have the following units: 

i. Steering Committee (SC) 

ii. Operations Committee (OC) 

iii. Program Management Unit (PMU) 

The composition of each of the above units will be in line with the approach described in 

Section 3 of Volume III of the RFP or as decided by ASI. 

b. Project Director: The relationship under this Agreement will be operated by the Project 

Director appointed by each Party, who will provide the interface between the executive 

management of the respective Parties. 

Before signing of this agreement, ASI and the Implementation Agency shall each appoint a 

Project Director. In the case of Project, the Project Manager will be an individual who is 

appointed by Steering Committee. In the case of the Implementation Agency, the Project 

Manager will be an individual who is an organizational peer of Project Manager. In the 

event that either Party wishes to substitute its Project Manager it will do so in the manner 

in which the original appointment is made and notify the other Party of such substitution as 

soon as reasonably practicable but at the latest within fourteen days of the substitution. 

c. The Project Directors shall have responsibility for maintaining the interface and 

communication between the Parties. 



d. The Operations Committee (OC) of the e-Ticketing project has been constituted to 

monitor day to day progress of the project and provide approvals and suggestions for 

smooth Implementation and Operations of the project and shall be chaired by ADG-ASI. 

The Operations Committee will meet formally on, at least, a monthly basis at a time and 

location to be agreed between them. These meetings will cover, as a minimum, the 

following agenda items: (i) consideration of monthly Performance Reports; (ii) 

consideration of matters arising out of the Change Control Schedule; (iii) issues escalated 

in accordance with the escalation procedure as set out in this Schedule; (iv) matters to 

be brought before the Operations Committee in accordance with the MSA and the 

Schedules; (v) any matter brought before the Operations Committee by the 

Implementation Agency under this Article; and (vi) any other issue which either Party 

wishes to add to the agenda. 

e. In the event that there is any material factor which affects the delivery of the Services or 

the terms of payment as stated in the Terms of Payment Schedule (Schedule VI of this 

Agreement), the Parties agree to discuss in the Operations Committee any appropriate 

amendment to the Agreement or any Service Level Agreements or Statement of Works 

including any variation to the terms of payment as stated in the Terms of Payment 

Schedule. Any variation so agreed shall be implemented through the change control 

procedure as set out in the Change Control Schedule (Schedule I of this Agreement). 

9.3. Governance Procedures 

a. The Implementation Agency shall document the agreed structures in a procedures 

manual under the guidance and supervision of the Project Director/Manager of ASI. 

b. The agenda for each meeting of the Steering Committee and Operations Committee 

shall be set to reflect the discussion items referred to above and extraordinary items 

may be added either with the agreement of the Parties or at the request of either Party. 

Copies of the agenda for meetings of the Program Management Committee, along with 

relevant pre-reading material, shall be distributed at least one week in advance of the 

relevant meeting. 

c. All meetings and proceedings will be documented; such documents to be distributed to 

both Parties and copies shall be kept as a record. All actions, responsibilities and 

accountabilities arising out of any meeting shall be tracked and managed. 

d. The Parties shall ensure as far as reasonably practicable that the Steering Committee 

and Operations Committee shall resolve the issues and resolve the objectives placed 

before them and that members representing that Party are empowered to make 



relevant decisions or have easy access to empowered individuals for decisions to be 

made to achieve this. 

e. The Parties will proceed in good faith so that the Steering Committee and Operations 

Committee shall resolve the issues and smoothen the performance of the Project. 

9.4. Liaison Between the Sub Contractors 

The Implementation Agency shall participate with other sub-contractors, approved by 

ASI and coordinate the receipt and delivery of the Services in a regular programme of 

liaison between the Project Director of ASI or any other representative of ASI and each 

of the sub-contractors. 

9.5. Informal Dispute Resolution 

The parties agree to attempt to resolve all disputes arising under the Agreement, 

equitably and in good faith. To this end, the parties agree to provide frank, candid and 

timely disclosure of all relevant facts, information and documents to facilitate 

discussions between them/their representatives or senior officers 



10. SCHEDULE V 

INVOICING AND SETTLEMENT SCHEDULE 

a. In respect of its remuneration for the Services the Implementation Agency shall be 

eligible to receive payments in accordance with the Terms of Payments Schedule 

(Schedule VI of this Agreement). Subject to the specific terms of each Service Level 

Agreement, the Implementation Agency submit its invoices in accordance with the 

following principles: 

(i) ASI shall be invoiced by the Implementation Agency for the Services. Generally 

and unless otherwise agreed in writing between the Parties or expressly set out 

in the Service Level Agreement, the Implementation Agency shall raise an invoice 

as per the terms of payment as stated in this Schedule. 

(ii) Any invoice presented in accordance with this Article shall be in a form agreed 

with ASI. 

b. Invoices shall be accurate and all adjustments to or changes in the terms of payment as 

stated in the Terms of Payment Schedule shall be applied to the next payment invoice. 

The Implementation Agency shall waive any charge for a Service that is not invoiced 

within six months after the end of the month in which the terms of payment as stated in 

the Terms of Payment Schedule relating to such Service are authorized or incurred, 

whichever is later. 

c. Payments invoiced shall be made within 45 days of the receipt of invoice by ASI subject 

to adjustments if any for the previous performance. 

d. ASI shall be entitled to delay or withhold payment of any invoice or part of it delivered 

by the Implementation Agency under this Schedule where ASI disputes such invoice or 

part of it provided that such dispute is bona fide. The withheld amount shall be limited 

to that which is in dispute. The disputed amount shall be settled in accordance with the 

escalation procedure as set out in the Governance Schedule (Schedule IV of this 

Agreement). Any exercise by ASI under this Article shall not entitle the Implementation 

Agency to delay or withhold provision of the Services. 

e. The Implementation Agency shall pay all their sub-contractors in a timely fashion in 

accordance with a mechanism, which will not prejudice the objective of Project. 

f. If any amount is due and payable by the IA to ASI/ Government, the same shall be 

recoverable as arrears of land revenue, in addition to other avenues legally available 

under this agreement. 



11. SCHEDULE VI 

TERMS OF PAYMENT SCHEDULE 

Payments to the IA shall have two components - During implementation and EQI Payments 

S. 

No. 

Project Milestone Payment (percentage of total Contract 

1. Implementation of Solution Go-Live for Round 1 

and Round 2 

2. Implementation of Solution Go Live for Round 3, 4 

& 5 

3. Total Operation & Maintenance Support 

A 

Post Implementation Phase including: 


Technical Support & Helpdesk 

Year 1 Operation & Maintenance Support 

B Year 2 Operation & Maintenance Support 

C Year 3 Operation & Maintenance Support 

value) 

50 % of Infrastructure & Application 


Cost 

Balance 50 % of infrastructure & 

Application cost 




Equal Quarterly installments


D Year 4 Operation & Maintenance Support 

E Year 5 Operation & Maintenance Support 

Terms of Payment for IA 



The e- Ticketing project shall follow a government led bought out model wherein IA will 

be required to finance all the expenses, capital and operational, related to their scope of 

work in this project. ASI shall pay them back all the above expenditure subject to certain 

terms and conditions described below: 

a. The entire cost of design, customization, implementation, operation and maintenance 

of the e-Ticketing project shall be borne by the IA. 

b. The IA would be paid by ASI for the above expenditure strictly as per the rates and 

amounts quoted by the IA in their commercial proposal and agreed by ASI. 

c. Payment will be subject to strict adherence to SLA signed between ASI and IA and 

subject to SLA credit/ debit points calculated by the team designated by ASI for every 

quarter as per the agreed methods, processes and tools. 

d. Payment shall be subject to penalty adjustment, if any, revealed during the SLA credit/ 

debit calculation or otherwise. 

e. Cost of third party audits, if any, shall be borne by ASI. 

f. ASI will make all efforts to make payments to the Bidder within 45 days of receipt of 

invoice(s) and all necessary supporting documents. 

g. All payments agreed to be made by ASI to the Bidder in accordance with the Bid shall be 

inclusive of all statutory levies, duties, taxes and other charges whenever 

levied/applicable, if any, and ASI shall not be liable to pay any such levies/ other charges 

under or in relation to this Contract and/or the Services. 



h. No invoice for extra work/ change order on account of change order will be submitted 

by the Bidder unless said extra work /change order has been authorized/approved by 

the ASI in writing in accordance with Change Control Schedule. 

i. The Contract would be signed for a period of Six years that includes one year of 

implementation and 5 years of operations and maintenance. Based on the performance 

of the Implementation Agency, ASI may decide to extend the period of contract by 2 

years. The Contract rates for the extended 2 years would be based on the rates of AMC 

for 4 th year and would be negotiable between the Bidder and the ASI. ASI is not bound 

to extend the contract period by two years. 

j. The Bidder needs to provide rationale for the commercial quotes provided. ASI holds 

the right to ask for an explanation of the rationale from the Bidder 

k. In the event of ASI noticing at any time that any amount has been disbursed wrongly to 

the Bidder or any other amount is due from the Bidder to ASI, ASI may without 

prejudice to its rights recover such amounts by other means after notifying the Bidder 

or deduct such amount from any payment falling due to the Bidder. The details of such 

recovery, if any, will be intimated to the Bidder. The Bidder shall receive the payment of 

undisputed amount under subsequent invoice for any amount that has been omitted in 

previous invoice by mistake on the part of ASI or the Bidder. 

l. All payments to the Bidder shall be subject to deductions of tax at source under Income 

Tax Act and other taxes, and deductions as provided for under any law, rule or 

regulation. All costs, damages or expenses which ASI may have paid or incurred, for 

which under the provisions of the Contract, the Bidder is liable, the same shall be 

deducted by ASI from any dues to the Bidder. All payments to the Bidder shall be made 

after making necessary deductions as per terms of the Contract and recoveries towards 

facilities, if any, provided by the ASI to the Bidder on chargeable basis. 

EQI PAYMENTS 

The IA shall be paid in Equated Quarterly Installments (EQI) as per the services provided to ASI 

in accordance with the price quoted by the bidder in his commercial proposal. The EQI 

Payments to the IA shall start only after the Final Go-Live of the e-Ticketing Project. 

The payment to IA shall be made at the end of each quarter only on receipt of invoices along 

with following supporting documents: 



A Report from the Performance Management System (SLAs) 

Any other document necessary in support of the service performance 

acceptable to ASI 

(I) The payment period shall be for the Agreement period of 5 years (20 EQIs) from the 

date of acceptance & Final Go-Live of e-Ticketing Project. 

(II) Payment to the IA for each quarter shall be paid only after due deduction of any 

penalties as per the SLAs. 

(III) Penalty details for e-Ticketing Project are furnished in Schedule VIII of Volume III of 

this RFP. 

1. IA Event of premature exit: In the event of premature termination of the Agreement 

prior to the completion of the Term by the IA, ASI shall forfeit the performance bank 

guarantee (PBG). In such case IA shall transfer the complete assets procured exclusively 

for ASI including hardware, software and licenses to ASI. 

2. A“I ill ot pa a osts of IAs odut of usiess, eept the paets stated i this 

Schedule. 

3. There will be no payments by ASI to IA to compensate for loss of business or wrong 

calculations. Costs of any investments to ensure IA delivery will be borne by IA. 

4. It is clarified here that there will be no payment upon transfer of the Assets pursuant to 

the expiry or earlier termination of the Agreement. 



12. SCHEDULE VII 

CHANGE CONTROL NOTICE 

Change Control Note CCN Number: 

Part A: Initiation 

Title: 

Originator: 

Sponsor: 

Date of Initiation: 

Details of Proposed Change 

(To include reason for change and appropriate details/specifications. Identify any 

attachments as A1, A2, and A3 etc.) 

Authorized by ASI Date: 

Name: 

Signature: 

Received by the 

Implementation 

Agency 

Name: 

Date: 



Signature: 

Change Control Note CCN Number: 

Part B : Evaluation 

(Identify any attachments as B1, B2, and B3 etc.) 

Changes to Services, charging structure, payment profile, documentation, training, 

service levels and component working arrangements and any other contractual issue. 

Brief Description of Solution: 

Impact: 

Deliverables: 

Timetable: 

Charges for Implementation: 

(including a schedule of payments) 



Other Relevant Information: 

(including value-added and acceptance criteria) 

Authorized by the 

Implementation Agency 

Name: 

Signature: 

Change Control Note 

Part C : Authority to Proceed 

Implementation of this CCN as 

submitted in Part A, in accordance with 

Part B is: (tick as appropriate) 

Approved 

Rejected 

Requires Further Information (as 

Date: 

CCN Number : 



Follows, or as Attachment 1 etc.) 

For ASI and its nominated agencies 

Signature Signature 

Name Name 

Title Title 

Date Date 

For the Implementation Agency 



13. SCHEDULE VIII 

Index 

Background 

MODEL OPERATION & MANAGEMENT SERVICE LEVEL AGREEMENT 

Article i – definitions and general purpose 

1. Definitions 

2. Structure 

Article ii – initialisation phase 

BETWEEN 


ASI 

AND 

Implementation Agency of e-Ticketing Project 

1. Objectives and scope of contract 

2. Commencement and duration of this SLA 

Article iii – financial issues 

1. Terms of payment 

Article iv – interpretation 

1. Applicability of the msa


MODEL SERVICE LEVEL AGREEMENT 

THIS AGREEMENT is made this _______________ day of ______________ 2012. 

BETWEEN: 

1. The President of India, acting through Director General, Archeological Survey of India, 

under the Ministry of Culture, Government of India, Janpath, New Delhi-110001 

heeiafte alled the A“I, hih te o epessio uless eluded o epugat 

to the subject or context shall mean and include its successors-in-office and assigns of 

the FIRST PART; 

AND 

2. ______, a company registered under the Indian Companies Act, 

WHEREAS: 

1956 having its registered office at _______ and place of business at 

____ (hereinafter referred to as "Implementation Agency", which expression, 

unless excluded or the context otherwise required hereof includes its successors, 

administrators and assigns) represented through its __ ___, who is duly authorized by the Implementation Agency to execute this 

agreement of the SECOND PART. 

A. ASI and [__________________] have entered into a Master Services Agreement dated 

[__________] (the "MSA"). 

B. In accordance with Article 1.2 (b) of the MSA, ASI and Implementation Agency wish to 

enter into this Service-Leel Ageeet Ageeet/“LA o the following terms. 



13.1 Article 1 – Definitions And General Purpose 

13.1.1 Definitions 

In this Agreement, unless the context requires otherwise: 

Agreement/Service Level Agreement /SLA" means this Agreement, together with its 

Appendices; 

"ASI Data" means all proprietary data of ASI which the Implementation Agency obtains, 

possesses or processes in the context of providing the Services to the users pursuant to 

this SLA; 

"Parties" means ASI and Implementation Agency for the purposes of this SLA, and 

"Party" shall be interpreted accordingly; 

"Service Level" means the level of service and other performance criteria which will 

apply to the Services as set out in Appendix A, in the form of SLA Metrics, effective 

during the Term of this SLA; 

"Term" means the duration of this SLA as defined in Article 2.2 of this SLA; 

"Terms of Payment" means charges for the Services in accordance with the Terms of 

Payment Schedule as stated in the MSA. 

13.1.2 All Appendices and other attachments to this SLA are hereby incorporated as a part of 

this SLA by this reference. 

13.1.3 References to any statute or statutory provision include a reference to that statute or 

statutory provision as from time to time amended, extended, re-enacted or 

consolidated and to all statutory instruments made pursuant to it. 

13.1.4 Words denoting the singular shall include the plural and vice versa and words denoting 

persons shall include firms and corporations and vice versa. 

13.1.5 Unless otherwise expressly stated, the words "herein", "hereof", "hereunder" and 

similar words refer to this SLA as a whole and not to any particular Article, Appendix or 

other subdivision. The words "include" and "including" shall not be construed as terms 

of limitation. The words "day" and "month" mean "calendar day" and "calendar month" 

unless otherwise stated. Where, because of a difference in time zone, the calendar day 

or calendar month in one Country differs from another Country, then the calendar day 

or calendar month shall be deemed to be the calendar day or calendar month applicable 

to India. The words "writing" and "written" mean "in documented form", whether 

electronic or hard copy, unless otherwise stated. 



13.1.6 The headings and use of bold type in this SLA are for convenience only and shall not 

affect the interpretation of any provision of this SLA. 

13.1.7 Structure 

This SLA shall operate as a legally binding services agreement specifying terms which 

apply to the Parties and to the precision of the Services by the Implementation Agency 

to ASI under this SLA and the MSA. 

13.2 Article II – Initialization Phase 

13.2.1 Objectives And Scope Of Contract 

Project Vision 

ASI proposes e-Ticketing initiative to harness the power of ICT Platform for its vision 

”To esure trasparet, eas, efficiet ticketig sste usig ICT to facilitate world 

class Visitor eperiece” 

The Implementation Agency hereby agrees to provide Services to ASI, conforming to the 

specified Service Levels, which will ensure the following objectives are met. 

The key objectives of e-Ticketing initiative are: 

a. Provide procurement of tickets through the web through a centralized e ticketing 

solution with online payment facility 

b. Poide poueet of tikets at the Poit of “ale at ouets though a 

centralized e ticketing solution 

c. To increase the efficiency and improve monitoring and administration of ticketing 

d. To increase transparency and accountability to the ticketing system 

e. To improve visitor experience through issuance and validation of tickets 

electronically 

To meet the aforesaid objectives the Implementation Agency will provide the Service 

Levels in accordance with the performance metrics for Project Implementation and 

Operational Level as applicable which are more particularly described in Appendix A of 

this SLA. on the date on which it is executed by ASI and the Implementation Agency 

heeiafte the Effetie Date ad shall, uless teiated ealie i aodae ith 

its terms or unless otherwise agreed by the Parties, expire on the date on which this SLA 

expires or terminates for any reason, which shall be 5 years from the Effective Date of 

this SLA. The SLA shall be coterminous with the MSA. 



13.3 Article III – Operation And Maintenance Phase 

(As referred in Section 8, Operational Requirements at volume I of this RFP) 

13.4 article IV – financial issues 

13.4.1 TERMS OF PAYMENT 

In consideration of the Services and subject to the provisions of the MSA and this SLA, 

the ASI shall pay the charges to the Implementation Agency in accordance with the 

Terms of Payment Schedule of the MSA. 

13.5 Article IV – Interpretation 

13.5.1 APPLICABILITY OF THE MSA 

Apart from the provisions as set out hereinabove, the terms and conditions stated in the 

MSA shall apply mutatis mutandis to this SLA. In the event of a conflict in interpretation 

of any Article in the MSA and the SLA, the provisions of the MSA shall prevail. 

WITNESSES 

1. 

2. 

Signed by: 

IN WITNESS WHEREOF the Parties have by duly authorised representatives set their 

respective hands and seal on the date first above written in the presence of: 

(Name and designation) 

For and on behalf of President of India 

(FIRST PARTY) 

Signed by: 

(Name and designation) 

(IMPLEMENTATION AGENCY) 



S. 

No. 

Service 

Parameter 

A) Project Implementation SLAs: 

1 Technical 

A Time taken to 

generate each 

ticket using e- 

Ticketing Solution 

using 

POS 

Application 

B Time taken to 

validate each ticket 

at entry gate 

Service level Measurement Metrics 

The time taken by application 

in printing a ticket using eticketing 

application 

The time spent for 

authenticating the generated 

ticket 

POS Application : 6 Minutes for 

1000 tickets 

Less than 200 milli-seconds 

(Round trip time) 


Penalty 

Slab1: >7 to 10 TO 1 to 

3 to 


C Erroneous tickets 

reported 

D e-Ticketing 

application service 

availability at DC 

and DR 

(Centralized) - 

Server Availability 

for Online Module 

The number of erroneous 

tickets reported by the visitors 

(including Foreigner and Indian 

visitors) 

The availability of all e- 

Ticketing application services 

at DC and DR should be 

greater than 99.982% in a 

quarter excluding the 

scheduled maintenance time. 

System should be able to print 

the Tickets and verify the tickets 

Analysis of event logs performed. 

IA shall ensure that all relevant 

events are logged and such logs 

are made accessible to ASI 

appointed agency for review / 

report. End to end loop back 

mechanisms must be established 

for checking the availability of 

services. Non-availability of even 

one of the agreed services would 

amount to no service available 

for the purpose of this SLA and 


Penalty – 

Slab 1: 0.5% of EQI 

Slab2: 1% of EQI 

Penalty – For each of the 

erroneous ticket reported to the 

system, the penalty shall be ten 

times of the ticket price. System 

should be able to record such 

instances 

Slab1: Application availability - 

99.00 % to 99.982% 

Slab 2: Application availability – 

99% to 97.00% 

Slab 3: Application availability 

below 97.00% 

Penalty – Slab 1: 1% of the EQI 

Slab 2: 5% of the EQI


E e-Ticketing 

Application 

Response Time 

Service Availability 

for Online Module 

The average application 

response time for users (time 

taken for loading of a web 

page) should not exceed 

1. 7 Sec for Portal home page 

2. 10 sec for forms and 

3. 20 Sec for user query 

The following mentioned 

services are critical to e- 

Ticketing online booking 

solution which shall be 

measured for the purpose of 

this SLA: 

Generation of a ticket 


thus breach Slab 3: 10% of the EQI 

Application response time will be 

measured on the basis of 

automated reports. 

The data should be captured 

through automated tools at least 

1 hour during the business hours. 

Data during business hours can 

only be used for calculations of 

average response time. 

Any scheduled downtime should 

not be included in the calculation 

of application response time. 

The application should be 

accessible for the ticket issuers, 

verifiers and to ASI management 

during the regular business 

Slab 1: Average Response Time 

between 8 seconds and 10 

seconds for portal home page. 



seconds for portal home page. 


above 13 seconds for portal 

home page 



seconds for forms. 


between 15 seconds and 

20seconds for forms.


Online Transaction 

Generation of 

automatic mail / SMS 

Notifications 

Web based Help Desk 

hours. The availability should be 

close to 99.99% 



above 20 seconds for forms. 



seconds for user query. 


between 26 seconds and 

30seconds for user query. 


above 30 seconds for user query. 

Penalty 

Slab 1: 1% of the EQI 

Slab 2: 2% of EQI 

Slab 3: 5% of the EQI 

Note: Precision of upto 2 

decimal points for all average 

times. Precision of 0.5 or less will 

be equivalent to lower figure 

and above 0.5 will be equivalent 

to higher figure. IA is expected to


2) Operation Level SLAs 

. 

A 

Help desk 

Response time: 

is the time in 

which query has 

been responded 

and the support 

resource is 

allocated/ site 

visited after 

reporting to 

helpdesk. 

Help desk 

resolution time: 

Quer 

y 

Maximum 

response 

time ( 

During 

Business 

Hours) 

Res 

olut 

ion 

tim 

e 

S1 30 Min 2 

Hrs 

Record the number of 

instances when Response 

time and/or resolution time 

is exceeded under each 

category of S1 and S2. 

Note: 

S1 stands for high-level 

support and S2 stands for 

low-level support. 


record a minimum of 50 data 

points per quarter. 

S1 Response time: 0.2 % of EQI 

S1 Resolution time: 1% of EQI 

S2 Response time: 0.1% of EQI 

S2 Resolution time: 0.4% of EQI 

Note: All values are per instance.


Defined as 

Time in which a 

complaint / 

query is resolved 

after it is 

reported to IA 

Support team 

B Reconciliation of 

revenue via 

Ticketing 

application vis-àvis 

Cash collected 

(for Online & POS 

Module) 

S1 2 Hrs( 

Non 

Business 

Hours) 


1 

Bus 

ine 

ss 

day 

S2 1 hour 1 

bus 

ine 

ss 

day 

S2 2 hour 

(Non 

business 

hours) 

No. of tickets sold should tally with 

revenue generated for that day 

100% For any gap in the reconciliation, 

the IA shall be penalized two 

times of the revenue gap 

reported by the system


C Operational 

Efficiency 

Note: 

Operational Efficiency measures shall 

include the following but not limited 

to: long queues at issuing and entry 

gates, 

Pre-defined surveys 

conducted by Monument 

Incharge on a daily basis 

(one each in morning and 

evening shift) and Random 

monthly survey by the Circle 

Head for all the monuments. 

Measure – The counter 

should facilitate atleast 200 

visitors in hours time 

1. The SLA measurement tool provisioned by IA shall be tested and certified for its accuracy, reliability and completeness by a 3 rd 

Party before it is deployed. 


Penalty:


14. SCHEDULE IX 

Progressive Rollout Approach with Timelines 

IMPLEMENTATION SCHEDULE 



Heritage 

Monuments & 

Category A 

Monuments ) 


the Annexure) 



Monuments & 

Category A 

)Monuments 



Annexures) 

Centralized 





Application 

Centralized 





Application 

Centralized 




T + 14 weeks 

T +26 weeks 

T + 36 weeks 






Annexures) 


Table 1: Timelines of the Project 

Project Implementation Schedule 


Annexures) 


Application 

Centralized 





Application 


application 

T + 46 weeks 

T + 52 weeks 



weeks) 



2. Site preparation and Procurement of hardware for core 

infrastructure of DC, DRC 


T+6 

T+8







Monuments 



Monuments 






Round 2 



locations 





locations 




T+9 

T+10 

T+12 

T+14 

T+26 

T+26 

T+36 

T+ 36 

T+ 46 

12. e- Ticketing documentation and Project documentation T+46




locations 




Support 

Table2: Implementation Schedule 

*T - indicates the project kick-off date 

T+ 46 

T+52 

T+52 to 312 

Bidders are advised to study the implementation approach carefully and propose the technical 

solutio ased o the ipleetatio appoah. It is epeted that fo go-lie of eah oud, 

Bidder would provide, application hosting, enable client infrastrutue ad tai A“Is 

personnel. 

All the modules presented above are defined in Volume 1 of this RFP document. 

- End of Document -

Request for Proposal for e Ticketing Project - Archaeological Survey ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?