Feeds

Big Blue red-faced over Congestion charge crash

First day fumble of new systems

High performance access to file storage

Things did not go entirely smoothly for IBM on its first day in control of Transport for London's Congestion Charge systems yesterday.

Capita set up the system and ran it for five years before TfL handed the contract to IBM in October 2007. Some staff were moved across and new systems put in place.

But sources told The Register on the morning of the first day that the system had not been live tested and staff were overrun with complaints.

A TfL spokeswoman said: “We apologise to customers for any problems they are experiencing since the transfer of systems to our new contractor this weekend. There have been some issues with accessing the online Congestion Charging payment accounts this morning, which the contractor is working to resolve as soon as possible.

"Customers should be assured that we are making arrangements so that no one will be penalised as a result of any problems today."

Error messages on the website warned people that there were "intermittent problems". But our insider complained that the transfer was not properly planned and problems were therefore inevitable. They said it was possible the system could send out penalty charge notices incorrectly because either people could not pay or the system would fail to record payments.

But TfL, which admitted there had been a high volume of calls to its help and payment lines, insisted that any teething problems would be fixed within 48 hours.

People needing to pay the congestion charge were advised not to use their existing registered accounts but should instead pay without registering. You can also pay via the call centre, or local shop, until midnight tomorrow without getting fined.

If any Register readers had problems with the system yesterday, please let us know via comments, or email me directly by clicking on the byline at the top of this story. ®

High performance access to file storage

More from The Register

next story
Android engineer: We DIDN'T copy Apple OR follow Samsung's orders
Veep testifies for Samsung during Apple patent trial
One year on: diplomatic fail as Chinese APT gangs get back to work
Mandiant says past 12 months shows Beijing won't call off its hackers
Big Content goes after Kim Dotcom
Six studios sling sueballs at dead download destination
Alphadex fires back at British Gas with overcharging allegation
Brit colo outfit says it paid for 347KVA, has been charged for 1940KVA
Jack the RIPA: Blighty cops ignore law, retain innocents' comms data
Prime minister: Nothing to see here, go about your business
Singapore decides 'three strikes' laws are too intrusive
When even a prurient island nation thinks an idea is dodgy it has problems
Banks slap Olympus with £160 MEEELLION lawsuit
Scandal hit camera maker just can't shake off its past
France bans managers from contacting workers outside business hours
«Email? Mais non ... il est plus tard que six heures du soir!»
Reprieve for Weev: Court disowns AT&T hacker's conviction
Appeals court strikes down landmark sentence
US taxman blows Win XP deadline, must now spend millions on custom support
Gov't IT likened to 'a Model T with a lot of things on top of it'
prev story

Whitepapers

Mainstay ROI - Does application security pay?
In this whitepaper learn how you and your enterprise might benefit from better software security.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.