A transit operational planning process includes four basic components performed usually in sequence: (1) network route design; (2) setting timetables; (3) scheduling vehicles to trips; and (4) assignment of drivers. This planning process is extremely cumbersome and complex and often creates confusion in its interrelationships among researchers and practitioners. The purpose of this work is to construct a framework and to provide an overview and examples of certain practical methodologies aimed at solving the transit scheduling problems. In the past 20 years, a considerable amount of effort has been invested in the computerization of the four components mentioned above. This is in order to provide more efficient, controllable, and responsive schedules. Nonetheless, despite the software used, no system is yet able to solve large scheduling problems, and manual intervention is necessary. There is a need to bridge the gap between the software system designers and the transit schedulers via the identification and organization of all the elements involved, including the current availability of data. This work emphasizes certain data needs along with examples for crystallizing and clarifying the transit scheduling undertaking. It is suggested that most of the scheduling tasks can be performed automatically, but it is preferable to undertake some of them through a conversational man-computer mode.
No takes yet. Share an insight, caveat, or question.
Avishai Ceder (2002) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: