Request for Proposal for e Ticketing Project - Archaeological Survey ...
Request for Proposal for e Ticketing Project - Archaeological Survey ...
Request for Proposal for e Ticketing Project - Archaeological Survey ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
RFP <strong>for</strong> e-<strong>Ticketing</strong> Solution Volume-I<br />
5. Functional Requirements - E-ticketing System<br />
The proposed e-ticketing system will meet the requirements of online booking by visitors<br />
and providing them ease of convenience. The e-ticketing solution will also integrate with<br />
Point of Sale (PoS) solutions which will be integrated so as to create an instantaneous record<br />
of tickets issued, and ensuring monitoring of the visitor traffic. The key functionalities of an<br />
e-ticketing solution include:<br />
5.1 Web based online ticket<br />
The implementation Agency (IA) is expected to build a plat<strong>for</strong>m which will integrate with<br />
A“Is eistig esite fo the iteet tiket ookig. The solutio should eale the isitos<br />
to book tickets online.<br />
5.1.1 Foreign Visitors<br />
1. The system shall allow relevant data like name , nationality, passport no., email Id,<br />
no. of visitors, etc. to be captured <strong>for</strong> issuance of internet ticket<br />
2. The system shall also allow data such as Date, No. of Monuments. For example the<br />
system shall allow to book <strong>for</strong> multiple monuments<br />
3. The system will allow ticket booking <strong>for</strong> multiple monuments within one circle only<br />
at a time<br />
4. The system should also capture details of differently abled visitor requirements <strong>for</strong><br />
instance , wheelchair services where available<br />
5. The system should send email alerts regarding booking details<br />
6. The printed internet ticket will have all data captured during the time of booking<br />
7. The system should send email alerts to visitors who have booked earlier on special<br />
exigencies such as bandh, security threats, VIP visits etc.<br />
8. The system should allow the visitor to take a print out of the ticket at the time of<br />
booking or enable printing of ticket at users convenience.<br />
9. The system should allow currency converter<br />
10. The ticket should support verification / authentication feature i.e. barcode<br />
11. The system should allow integration with payment gateways<br />
12. The system should also allow integration with other service providers to provide<br />
value added services<br />
13. The interface should provide web helpdesk <strong>for</strong> any visitor queries, grievances etc.<br />
The system will not allow ticket booking where the monuments have been closed<br />
temporarily due to reasons such as preservation, security etc. where applicable<br />
14. The system will allow configuration of ticket validity period<br />
Archeological <strong>Survey</strong> of India, Ministry of Culture Page 23 of 107
Change language