Transport for London contractor Transys crashes the Oyster Travel Card system for the second time in 2 weeks i.e. since Saturday 12th July.)
According to this TfL press release:
25 July 2008
A Transport for London spokesperson said:
"There was a technical problem with Oyster card readers at London Underground stations this morning which affected Oyster pay as you go cards only. Oyster card readers on the bus and tram network were unaffected.
"The problem has now been resolved and card readers are progressively coming back on-line at London Underground stations.
"Cards have not been disabled and so can continue to be used as normal. We will automatically refund any passengers who may have been charged the maximum £4 fare as a result of not being able to touch in and out at the beginning and end of their journeys this morning. Oyster card holders need take no further action.
"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). Transys has also issued a statement today confirming that they are taking steps to ensure that this does not happen again, that they will undertake a root cause analysis and, like us, apologising for any inconvenience caused to our customers."
The Transys consortium website says:
TranSys statement : 25/07/08.
The technical problem which affected Oyster readers at London Underground stations has now been resolved and all stations are all fully functional. The problem affected pay as you go users only.
Steps are being taken to ensure that this does not happen again and we will undertake a full root cause analysis.
TranSys regrets any inconvenience caused to Transport for London's customers.
As Transport for London has made clear, Oyster cards are not being disabled and automatic refunds will be made to any customers charged maximum fares as a result of not being able to touch in and out at the beginning and end of their journeys. Oyster card holders need take no further action.
How dare they implement software changes to a live production system, without first checking them thoroughly on a realistic test system ?
These repeated failures are indicative of faulty management, who will probably try to shift the blame onto a junior employee. Will any senior management heads roll ?