Oyster problems: Blame Transys
During today's Oyster failure, TfL put out a press release that includes the first hint of what the problem is:
This problem, like the recent issue, resulted from incorrect data tables being sent out by our contractor, Transys (a consortium of the firms EDS and Cubic).They're probably referring to new fare and routeing data (there are a few changes due). No word yet on how this caused 65,000 cards to be permanently destroyed last time this happened.
3 comments:
Does anyone know of anybody whos card actually was destroyed last time? I know of several people who used the tube and busses and tapped in during the hours the system was down, but all of them report their cards work fine. One person paid for a bus journey which was deducted as normal, then refunded! I guess they can't be sure who is due a refund and who isn't so simply refunded all payments taken.
This morning there was no chance of trying to tap in, there were signs attached to every reader, a woman stood in the middle of them screaming 'Do NOT tap in, do NOT tap in' as well as an announcement repeating a similar message.
At Wimbledon (mainline) this morning the barriers were operating as usual and I touched in fine with my annual season ticket on Oyster. Not sure what happened to everyone using PAYG on the district line though...
Bank station were letting everyone through - much quicker to leave the W&C platform than usual! Need to do this more often.
My card was destroyed on the Saturday when the Oyster system failed. NOT very happy...
Post a Comment