London Transport (uk.transport.london) Discussion of all forms of transport in London.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #21   Report Post  
Old February 13th 15, 12:18 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Sep 2008
Posts: 4,877
Default Oyster charging for journeys that don't happen

In article , (Roland Perry)
wrote:

In message , at
12:03:34 on Fri, 13 Feb 2015, David Cantrell
remarked:
The result - I was charged for entering and exiting at Waterloo, and
then charged again for my actual journey.
It's not an error, the system is operating as programmed. (You're a
programmer, no? Technology, including Oyster, doesn't just do it's own
random thing.)


Operating as programmed isn't the same as operating without error. If it
were then there would be no such thing as a bug.

Nor is operating as *specified* the same as operating without error. If
it were then specifications would never change.

The Oyster website says that they deliberately make this charge "to
avoid fare evasion". But I'm really struggling to think of a way of
evading fares that would involve touching in, and then touching out less
than ten minutes later at the same station. I might just about be able
to make a round trip from Waterloo to Vauxhall and back again in ten
minutes with a great deal of luck, but it's fairly obvious that the
potential costs of people avoiding that fare are far less than the
excess income generated.

It is clear to me that the specification is faulty in this case.


The failure mechanism would appear to be someone touching in, and
then touching out on a gate but failing to go through the gate. So
they are still "airside", and capable of catching a train somewhere.

This is such a fundamental fraud vector that whoever designed the
system to allow it (while penalising innocent passengers whose
platform was changed at the last minute) should be hung out to dry.


What do you suggest?

--
Colin Rosenstiel

  #22   Report Post  
Old February 13th 15, 12:32 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Aug 2003
Posts: 10,125
Default Oyster charging for journeys that don't happen

In message , at 07:18:41
on Fri, 13 Feb 2015, remarked:
It's not an error, the system is operating as programmed. (You're a
programmer, no? Technology, including Oyster, doesn't just do it's own
random thing.)

Operating as programmed isn't the same as operating without error. If it
were then there would be no such thing as a bug.

Nor is operating as *specified* the same as operating without error. If
it were then specifications would never change.

The Oyster website says that they deliberately make this charge "to
avoid fare evasion". But I'm really struggling to think of a way of
evading fares that would involve touching in, and then touching out less
than ten minutes later at the same station. I might just about be able
to make a round trip from Waterloo to Vauxhall and back again in ten
minutes with a great deal of luck, but it's fairly obvious that the
potential costs of people avoiding that fare are far less than the
excess income generated.

It is clear to me that the specification is faulty in this case.


The failure mechanism would appear to be someone touching in, and
then touching out on a gate but failing to go through the gate. So
they are still "airside", and capable of catching a train somewhere.

This is such a fundamental fraud vector that whoever designed the
system to allow it (while penalising innocent passengers whose
platform was changed at the last minute) should be hung out to dry.


What do you suggest?


Landside validators to confirm you've left the platform.
--
Roland Perry
  #25   Report Post  
Old February 13th 15, 03:38 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Jan 2015
Posts: 33
Default Oyster charging for journeys that don't happen

On Fri, 13 Feb 2015 13:32:50 +0000
Roland Perry wrote:
In message , at 07:18:41
on Fri, 13 Feb 2015, remarked:
What do you suggest?


Landside validators to confirm you've left the platform.


Nah, there's a far more simple solution - if no one goes through the gates
on a touch out (infra red beam not triggered) before they close THEN you
deduct a penalty fare otherwise you refund.

--
Spud



  #27   Report Post  
Old February 13th 15, 09:43 PM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Jul 2003
Posts: 329
Default Oyster charging for journeys that don't happen

On 13/02/2015 6:23 AM, Roland Perry wrote:

"If you touch in on a yellow card reader to make a journey and
then decide you don't want to make it or you can't because of
service disruption and touch out again to exit your Oyster card
will be charged. We apply charges to discourage fare evasion.
However, you may be able to get a refund if this happens."

The burden here is far too much on the innocent traveller.

The alternative is for the gateline assistant to let everyone out
*without* touching out, and then go to the Ticket Office to get the
touch *in* cancelled...except that's not an option at Waterloo because
SWT don't "do" Oyster at Ticket Offices, and even if they did, you'd
have missed half a dozen trains by the time you got to the front of the
queue. (Possibly a slight exaggeration).

A Ticket Office is unable to resolve a "double touch" where an OSI is
involved, as they can only cancel the last *exit* touch. So if you were
travelling Piccadilly Circus - Waterloo (LU) - Waterloo (NR) -
Wimbledon and such a situation occurred, the exit touch at Waterloo (NR)
would have to be cancelled, and then you'd have to go back down to the
Underground station and touch *out* again to close the journey
properly...assuming you were still within the maximum journey time.

Or you just wait 'til the following day and go to the Oyster website
(assuming your card is registered) or phone the Helpdesk and they'll
sort it out for you with significantly less faffing around...

Cheers,

Barry

  #28   Report Post  
Old February 14th 15, 07:38 AM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Aug 2003
Posts: 10,125
Default Oyster charging for journeys that don't happen

In message , at 22:43:23 on Fri, 13
Feb 2015, Barry Salter remarked:
On 13/02/2015 6:23 AM, Roland Perry wrote:

"If you touch in on a yellow card reader to make a journey and
then decide you don't want to make it or you can't because of
service disruption and touch out again to exit your Oyster card
will be charged. We apply charges to discourage fare evasion.
However, you may be able to get a refund if this happens."

The burden here is far too much on the innocent traveller.

The alternative is for the gateline assistant to let everyone out
*without* touching out, and then go to the Ticket Office to get the
touch *in* cancelled...except that's not an option at Waterloo because
SWT don't "do" Oyster at Ticket Offices,


What if the traveller was using Contactless - can the SWT ticket offices
deal with hiccups then?

and even if they did, you'd have missed half a dozen trains by the time
you got to the front of the queue. (Possibly a slight exaggeration).

A Ticket Office is unable to resolve a "double touch" where an OSI is
involved, as they can only cancel the last *exit* touch. So if you were
travelling Piccadilly Circus - Waterloo (LU) - Waterloo (NR) -
Wimbledon and such a situation occurred, the exit touch at Waterloo
(NR) would have to be cancelled, and then you'd have to go back down to
the Underground station and touch *out* again to close the journey
properly...


Would that require you to find someone to let you back airside in order
to come back with a touch-out? I'd be reluctant to touch-in, in case it
triggered yet another layer of problems.

assuming you were still within the maximum journey time.


Given that the exercise started when SWT cancelled a train, would Delay
Repay allow you to add the time queuing at the ticket office to the
overall journey delay?

Or you just wait 'til the following day and go to the Oyster website
(assuming your card is registered) or phone the Helpdesk and they'll
sort it out for you with significantly less faffing around...


What a performance! Just because SWT was a driver short.
--
Roland Perry
  #30   Report Post  
Old February 14th 15, 07:44 AM posted to uk.transport.london
external usenet poster
 
First recorded activity at LondonBanter: Aug 2003
Posts: 10,125
Default Oyster charging for journeys that don't happen

In message , at 16:38:53 on Fri, 13 Feb
2015, d remarked:
What do you suggest?


Landside validators to confirm you've left the platform.


Nah, there's a far more simple solution - if no one goes through the gates
on a touch out (infra red beam not triggered) before they close THEN you
deduct a penalty fare otherwise you refund.


The fare dodgers could just wave an umbrella/briefcase through the beam
to get it to falsely register their departure.
--
Roland Perry


Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Oyster error - how does this happen tim...... London Transport 46 November 6th 13 06:19 PM
They said it would never happen... Paul Scott London Transport 3 November 20th 09 01:04 PM
Why would this happen? Boltar London Transport 4 December 5th 07 10:56 AM
Oh dear.....I'm sure it wont happen. Malcolm & Nika London Transport 21 December 11th 04 11:37 AM
What will happen to KX Thameslink? Heliomass London Transport 46 April 13th 04 11:38 AM


All times are GMT. The time now is 12:00 AM.

Powered by vBulletin®
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 London Banter.
The comments are property of their posters.
 

About Us

"It's about London Transport"

 

Copyright © 2017