01.08.2013 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RFP <strong>for</strong> e-<strong>Ticketing</strong> Solution Volume-I<br />

5.1.2 Indian Visitors<br />

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

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 an email / SMS 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 / SMS alerts to visitors who have booked earlier on<br />

special exigencies such as bandh, security threats, VIP visitors, etc.<br />

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

booking or enable printing of ticket at users convenience.<br />

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

10. The system should allow integration with payment gateways<br />

11. The system should also allow integration with other service providers to provide<br />

value added services<br />

12. The interface should provide web helpdesk <strong>for</strong> any visitor queries, grievances etc.<br />

13. All screens and templates of the system should be in English and support Devanagari<br />

script where required..<br />

14. 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 />

15. The system will allow configuration of ticket validity period<br />

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

Entry pass however with data captured such as date, time, monument, no. of<br />

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

central database<br />

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

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

total value of ticket printed on the entry ticket and the system to reconcile the<br />

numbers in the central database<br />

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

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

system will reconcile the numbers in the central database<br />

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

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

the system will reconcile the numbers and the details in the central database<br />

Archeological <strong>Survey</strong> of India, Ministry of Culture Page 24 of 107

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!