UNIFIC CAPITULO 111: EXPEDIENTE TÉCNICO

13.6. Section C-8

“Currently KSRTC at Mysore has been using the e-Ticketing machine in the buses to issue tickets. It would be expected that through the communication system in the bus, the data on the number of tickets issued and count of passengers must be up loadable to the CCS at configurable time intervals. The proposed AVL-IS and PIS solutions at the CCS must support all e-Ticketing related functionalities and MIS/ reports.”

Do the ETMs used by KSRTC currently have capability to transfer data through the communication system in the bus?

Refer question 13.1

13.7. Who will provide the interface with the e-ticketing solution? What will be the data format/Data Structure of the output from e-ticketing Solution.

Refer question 13.1

13.8. Is there any integration expected at bus level for ticketing machine?

No

13.9. Not clear about “Seat Availability” and “Bus fare” display at bus stop terminal. How this will happen? which system will be responsible for the same?

Refer question 13.1

13.10. Electronic ticket sale machine and fare collection system. Is there a system that KSRTC has procured for the Fare collection and E-ticketing? Please provide technical descriptions.

Refer question 13.1

13.11. How you calculate the no of passenger boarded in the bus at particular bust stops? How you calculate the passenger density?

13.12. Bus stop utilization rate – no. of passengers boarding at different bus stops Enroute. How we calculate no of passengers boarding at different bus stops? Please clarify.

Refer question 13.1

13.13. Please provide the details of the E-ticketing machine, so we can check the compatibility with the VMU.

Refer question 13.1

13.14. Whether KSRTC will assist the bidders in associating with the ETM vendors?

Refer question 13.1

13.15. F-Req42. 12. It should enable operational managers to very easily create locations, routes, schedules and flexible ticket pricing plans using an intuitive user interface Please explain to relationship/dependency (if any) between ticket pricing planning and AVL system and how will they work together

The data generated from the ITS should facilitate analysis of the efficiency of the entire operations and it is from this perspective that this requirement needs to be understood. The operational managers need to evolve effective ticketing and pricing plans based on traffic density on different routes, deployment of additional buses to meet the increased traffic, facility to do different kinds of analysis on the pricing plans as part of it Management Information System.

13.16. What ticketing system is in use in Mysore? Ticket cost is fixed per trip, or per zone (distance)?

The ticket cost is based on distance and type of service.

13.17. The system of passengers counting inside the buses – what is used now and what protocol it is using (for integration with ITS)

Refer question 13.1

13.18. Integrate ITS solutions with existing applications. Please provide more technical detail on the existing KSRTC applications that the ITS solution has to interface with?

KSRTC is making use of Depot Computerisation Software for downloading ETMs. The existing system of KSRTC being used may be studied by Bidder and suitable solutions may be proposed to achieve the functional requirements.

13.19. Electronic ticket sale machine and fare collection system. Is there a system that KSRTC has procured for the Fare collection and E-ticketing? Please provide technical descriptions.

Refer question 13.1

13.20. (3). B-1-b Clause (1) under "Stakeholders' expectations for travelers at bus stops/stations" mentions availability of information related to "(Bus Numbers: Starting - Destination Point - en route stops), Schedule of the buses - ETA/ETD, Seat availability, approximate travel time in at least two languages - English and Kannada , point to point bus fares, types of buses - AC/Non-AC/Non-stop routes etc; accessibility to such information should be both visual and audio enabled". For having an accurate estimate of seat availability; there must be an accurate passenger counting system or alternately it must be either programmed so that driver can choose this option on driver screen. The accuracy may depend on many factors that include seating configurations modifications, standee capacities and pre- information about exit point of every passenger on board. Such a system could be accurate only in case of ticketing machines installed outside buses and provided passengers strictly adhere to entry and exit points. We wish to understand that under these circumstances, what would be the level of accuracy that you expect for calculating the seat availability?

Refer question 13.1

13.21. Ability to locate a bus at a given time in its track to estimate its arrival/departure time at the next destination, based on traffic density, distance, speed, bus occupancy, run-time information from the previous bus arrival time for the same location etc; the accuracy of the reduction time should not vary more than +- 2 minutes. . Bus Occupancy Status- This will be possible only after implementation of ETM - Is our assumption right? Traffic Density - How do we take this input in our system? . Does this also mean that we need to pre define different transit times for same route during different times of a day?

Refer question 13.1

13.22. Automated voice announcement should add on easily to the passenger counting system connected to the on-board ITS components. Is the passenger

counting system already installed in the buses? If yes what is the make, model, integration points and features available with it?

Refer question 13.1

13.23. Bus Equipment - Is there any passenger counting system installed in the buses? Is it required if there is no ticketing system? Can you explain the meaning of F-Req 46? How the passenger counting will impact the voice announcement?

Refer question 13.1

13.24.Section B-1-b Meeting Stakeholder Requirements

Information availability on Bus routes (Bus Numbers: Starting – Destination Point – en route stops), Schedule of the buses – ETA/ETD, Seat availability, approximate travel time in at least two languages – English and Kannada , point to point bus fares, types of buses – AC/Non-AC/Non-stop routes etc; accessibility to such information should be both visual and audio enabled.

1. 'Seat Availability' - it will not be possible to know real time seat availability in current scope as it would require Ticketing System Integration. Please confirm. 2. 'audio enabled' - what we understand is that as per current scope, bus stops/stations are not having audio PIS. Please confirm.

Refer question 13.1