"Neil Williams" wrote in message
...
Recliner wrote:

But there's also the issue of the journey time limit, which is where the
problem can arise. For example, let's say journey 1 lasts 80 minutes (90
allowed), and the next journey, from the same station, starts 15 minutes
later (20 mins OSI allowed). The Oyster system will try and combine these
into a single journey, but the combined journey may well exceed the
allowed
time, leading to two incomplete journeys.

A sensible solution for OSIs would be to add the time outside the system
while using an OSI to the maximum.

I don't think the time outside the system is critical to causing the problem
here (except in as much as making it possible to transact your genuine
business within the transfer time).

You're just as likely to "time out" on a through journey that "wasn't" if
you spend 15 minutes transferring as 2 minutes.

tim