We’ll have to wait to see where RBS lays the blame for Monday’s IT crash. Last time a bank’s IT system failed it was due to a scheduling problem with a critical service like batch processing.
At that time, the bank had no warning of the issue. It could have been building over time or it could have been as simple as someone making a change – planned or otherwise. What they didn’t have was visibility of their systems.
From a change perspective, it’s vital to be able to see how key applications are performing – and if a change is made, you need to see the impact it has on the operation of those services.
Regarding this week’s IT disaster, RBS' CEO Ross McEwan said: “"For decades, RBS failed to invest properly in its systems. We need to put our customers' needs at the centre of all we do. It will take time, but we are investing heavily in building IT systems our customers can rely on.”
Whilst under-investment may be a cause, RBS needs to be very cautious about throwing money at new technology, particularly if they are unable to see how that technology is then performing. They may well come up facing the same problems.
After all, you can only manage what you can see and understand.
- Published: 06 December 2013