Abstract

Rail operations are often disrupted by accidents that cause traffic to diverge from the scheduled operations, rendering it difficult to run the schedule as planned. In such a case, the operator must change the schedule to return to the original schedule. If passengers are delayed, a train operator may have a policy of economically compensating them (e.g., refunding ticket fare). Compensation amounts are usually determined by the length of the delay. As a result, it is critical to have a smart way of determining whether to accelerate trains to absorb delays, thus increasing energy usage, or to compensate passengers. This paper presents a mathematical model for determining the speed profile while taking passenger usage into account. The model determines the best sequence of operating regimes and switching points between them for a variety of different situations and train types, all while accounting for delays and passenger compensation policies. The aim is to reduce both the amount of energy consumed and the amount of compensation paid to passengers. There are constraints on traction and braking forces, train velocity, forces induced by vertical and horizontal track profile, and passenger compensation policy. The results of computational tests performed on practical problem instances of the Spanish rail operator RENFE are showed. The suggested approach is capable of producing strategies that strike an excellent balance between different managerial objectives.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.