Excel Services in Office 2007
There are lots of Microsoft bashers around, and they have lots of material to discuss at the moment. Apart from the recent cancellation of WinFs - probably the most singularly important feature of Windows Vista - there's the impending departure of Bill Gates, as well as the ongoing (if somewhat inflated) news of the clash between Google and Office, now that Google has a spreadsheet.
And its on the subject of spreadsheets that I thought I'd comment today. You see, Microsoft are about to release - as part of the next version of Office - a server version of Excel. And this is a release of some importance for banks.
Recently, I was working with a bank in Australia that told me - and I believe them - that it was possible that several hundred million dollars of value passed through them daily on the basis of figures calculated by Excel spreadsheets. Excel is an intuitively easy tool to use, and this makes it the best choice for business people that need to do things, such as traders who have to react quickly to market changes, or analysts who like to develop their models quickly. I've come across quite a few cases where Excel models are embedded in live, production systems in banks.
So Excel delivers business agility, but have you considered the potential liability if any of those spreadsheets are wrong? Imagine a multibillion dollar transaction going astray, simply because a calculation in a spreadsheet wasn't carefully checked by anyone other than the trader or analyst who created it in the first case. And Excel calculations are simply not that easy to check. How often have you been given a spreadsheet, and tried in vain to understand the logical behind the authors calculations?
That's where Excel Services comes in. Excel Services lets you impose IT disciplines on a business focused tool. With Excel Services, you load a spreadsheet into an environment where it can use live data from systems, be accessed by a browser, or be embedded into other applications. And this can all be done under change control, with the full set of dev, test, and production environments that are the norm for other mission critical systems. Even more importantly than that, it lets a bank do a couple of things that have been very complicated before: ensuring that there is only one source of the truth across a multitude of potential model authors; protecting any intellectual property and business secrets that might be embedded in the model; and finally, making a model universally accessible, regardless of whether a someone has a copy of Excel or not.
All this is very nice of course, since in a regime of Basel II and operational risk, you almost have to be looking at your library of Excel models and getting control of them back from the business people that created them. It is simply unacceptable - and potentially very expensive - to have a mission critical spreadsheet in existence outside the control of those processes which control every other system in a bank. Going back to the Australian bank I referred to earlier: they told me they had about 50,000 spreadsheets they needed to review and get control of to be sure they could comply with the latest regulations.
Banks thought they had a problem with islands of data in Access? The Excel problem is way, way, bigger for a financial institution. Frankly, I'd be willing to bet that the more entrepreneurial and fast moving the bank, the bigger the Excel problem must be.
Credit to Microsoft for providing a graceful way of handling the situation. Loading existing spreadsheets in a server that knows Excel is going to be way less expensive - and certainly quicker - than recoding all that business critical functionality. Microsoft, despite what detractors might say, have built a feature that more than justifies the cost of upgrading to the latest version if you're in financial services.
Although, to be quite frank, the primary feature of the Google spreadsheet is also that it can read Excel models and load them in a server. Not a server running on the premises of the bank of course, but its a server nonetheless. Perhaps not quite there in terms of what a bank needs, but an interesting, and indicative, development nonetheless (read my previous comments on Google in financial services here).
Recent Comments