Me, an American: “You guys have public transportation?”
Train is canceled today. Here’s a voucher for a Nazi-owned taxi company that’ll get you halfway home.
They figured out a loophole to improve the statistics: a train can’t be late if it never arrives.
Iirc for the DB a train is considered on time when it’s not later than 7 min on arrival. Which is a joke if you miss your following connection.
I’m not sure I agree. The real world is never going to run perfectly, so some slack must be included (either by adding buffer time to schedules, or using the way you mention). Of course there are examples like Japan that have done a really good job at optimizing these systems, but you won’t be able to successfully apply their approach to every country. Some locations require more work to achieve this, others require less.
Generally the closer you get to an “ideal” performance, the more costly every further improvement gets. If 7 min isn’t reasonable, what number would be? Say we manage to shave off two minutes, at twice the cost of the current system. Is that really worth it?
The better approach is to include reasonable slack time in people’s train schedules, while increasing frequencies so missing a connection doesn’t result in hour-long wait times.
I have this same argument with my spouse. If fifteen minutes late is “on time”, then change the arrival time and just be on time.
A train that doesn’t arrive at all is also not considered late.
Luckily the next train you have to take is also late, so nothing really changes. A system so broken that it works “perfectly”.
It’s a friendly rivalry among many European countries to boast about how shitty their railway companies are.
But but America!
The fuck are you on about?
Sitting in a train right now. It started half an hour late and on top of that we have to drive a detour because of an accident on the tracks. Ah well.
I understand the whole “it has to get worse before it gets better” angle when some railway sections have to be closed for a complete overhaul, but I feel like there’s an infrastructure equivalent to refeeding syndrome.
When your body has to make do with little-to-no food, it restructures its metabolism to deal with that. When you suddenly increase your food intake again, it can’t deal with that and you die. Instead, food intake must be slowly ramped up.
When an infrastructure provider has little money for repairs, they tend to take their most urgent “cannot be postponed” repairs, rank them, and do the absolutely most urgent “cannot be postponed” ones first. When they suddenly receive more money, there is a tendency to abandon this ranking system because all of these repairs are urgent “cannot be postponed” repairs and they no longer need to be ranked… which leads to collapse because of course the primary, the backup and the other backup route are being repaired at the same time, all three are in need of urgent “cannot be postponed” repairs!
I think the management structures of infrastructure providers should take this into account when a budget increase comes their way.
Their strategy so far is to close and overhaul lines completely. I think it is somewhat fair to expect that’s cheaper and faster than overhauling one side at a time. They prioritize by traffic and urgency of overhauls. It is a solid strategy - but it comes with major disruptions of long distance travel
