|
In the emerging markets, in something like 90 countries, our intention is to install a package to do bookkeeping and product processing that's being provided to us by an Indian software company in which we have a major interest. The company is called I-Flex, and the package is called Flexcube. We've already installed it in 13 countries, and we have a rollout strategy that takes us out over the next two years to cover all of the emerging-markets countries.
But it's not quite a simple deal to install the same set of software in every one of these countries, because...we have to interface with every regulatory or clearing agency in these countries. And we have to provide appropriate customer reporting and product information to meet the market needs. Our challenge is to create a consistent set of code that allows customization without violating the core of the system. That's a big challenge.
Which operating systems are used across the company? We're doing very little Linux; right now, we're just experimenting with Linux. We're running just about every other platform you might imagine. We run a great deal on IBM mainframes in our larger businesses, running IBM's operating system on the mainframes. We run our trading applications for Salomon Smith Barney primarily on Sun Solaris systems. We run our administrative applications with a lot of use of Microsoft software. Our selected e-mail platform is Exchange, and we're in the process of converting the whole bank to Exchange. We use Hewlett-Packard platforms in some parts of the world.
How do you decide what's more appropriate for each department? A couple of ways. Is there an application available that we might purchase that runs on one or another of these platforms? Or do the local people have expertise in selected systems, like HP in Europe or Sun Solaris in our trading environments in New York? Or are the requirements of this system such that we need to manage very large databases and have them run on a mainframe? For selected applications, we use the DB2 database heavily on the mainframe. We use SQL Server in the Microsoft environments. We use Oracle on a number of our applications, and Oracle is the database management system of choice for our procure-to-pay system. It will also be the selected platform for our human resources system, which is a PeopleSoft system. We use virtually every major platform, and it depends on the application's functional requirements and our degree of expertise among the team who has to deliver it.
What are you using on the desktop? On the desktop is Microsoft. We've been installing XP in small parts of our business, and that will be rolled out over time. But basically, it's Win 2000.
Is there enough power on the desktop now with your current crop of Pentium 4 machines? How do you decide when you need to upgrade those machines? We do not have a calendar-driven refresh cycle. What we do is look at the capacity utilization of the desktop systems depending on the business being supported. And we add to that the planned incremental applications that will be used on that desktop to see when we will need to increase capacity in order to support the client's requirements.
How often does that happen? It varies by business. In Salomon Smith Barney, we have 20,000 desktops supporting the retail business. In 1995, we installed a system across all of Salomon Smith Barney's retail business--for those 20,000-plus desktops--with the PCs that were available at the time. We refreshed those in 2000 because of the coming of decimalization in the securities business and the recognition that we had increased the applications that our retail financial consultants were relying on, and we saw performance tending to degrade. In the investment bank, where our research people drive their desktops very, very hard with a lot of applications and a lot of data requirements, we probably refreshed twice in the same period of time.
Are you launching any Web services? Our toe is in the water. We're doing work with .Net. We've got some things going on in the Travelers business, for example, and some work is also going on in the corporate investment bank. I won't say we're in it with both feet yet, but it is part of our strategy.
In the corporate investment bank, there's an initiative to deliver more comprehensive information to the institutional customer,...and (that) is a major project that brings together information from a variety of Citigroup sources in order to present data to those individuals. That is being worked on with .Net. With Travelers insurance, I think there's some agent systems being focused on .Net (technology). (The unit that issues) credit cards (is) also looking at employing .Net.
What's your impression so far? Does the reality match up to the hype? A lot of our decisions about using the platform are based on the business objectives of the entire system and how we think it can best be served. I think it's still early to make the call on how that's going to play out. I also think it depends on how you implement. We tend to implement by running the software in our own shop, and not using a hosted environment to run things. So the software we choose to employ has to be (able to run) in our own environments and has to give us the appropriate information (and) security protection that we need. It's tough to say whether Web services will satisfy everything we need in the near term. But we'll find out before we go whole hog.
What is your biggest disappointment so far with Web-based technologies? Today, every one of the millions of customers who are online can look at their accounts whenever they want to. If there is a production problem, then it's glaringly apparent to the whole world, whether or not it allows somebody to do something illicit or illegal. Our vulnerability is very high. What that really means is that the need for quality assurance in all of your processes--quality processing, do it right the first time, don't make an error when you install new versions of software or make enhancements to what runs--all those things become increasingly more important.
Earlier, you were talking about having Oracle and PeopleSoft on the back end. It sounds like you are launching some ERP (enterprise resource planning) applications.
We're rolling out major implementations across our businesses. One is in HR, which is a PeopleSoft implementation. We decided that we would install PeopleSoft across all of Citigroup. We literally are in the early stages of it, but we have made that commitment. Every business at the (human resources) level and the CEO level has signed on to using that system going forward.
What kind of return on investment (ROI) are you looking for when you launch PeopleSoft for your human resources department or other ERP systems?
We're looking for a reasonable ROI. I won't give you any numbers, but there is a reasonable cost payback in terms of reduced staff and based on better information to HR and business executives in running their businesses. If you consider the fact that we are in over 100 countries, we have a challenge in terms of getting consistent data collected and then presented to management to make decisions. So we see a tremendous opportunity to have a data warehouse that will give us all the information about our employees.
How soon do you expect it to start paying for itself? Less than two years.
Are you launching any CRM applications? We are, but in a different way. CRM is very heavily dependent on how you define it. What's your objective? Is it a call center solution? Is it a prospecting solution? Is it analytics that you want? Is it managing mail campaigns and follow-up? Each one of those might require a different kind of solution.
In the area of CRM, we've done considerable work to identify which CRM products make sense and have been either implemented or are in implementation across the businesses. We're heavy users of Siebel, which is the predominant vendor. But we're also users of Epiphany and Kana, and in one case, PeopleSoft CRM is being deployed.
Again, why the different decisions? The reason we made the different decisions was based on the specific objectives of the business in implementing a CRM solution. What we're doing there is we've created a center of excellence where we know what criteria one should be looking at to choose one or another of these products. We have encouraged the business IT people to work with the people with the knowledge--with the information about what's been or is being installed and what's driving it--in order to derive a conclusion about which vendor solution is the best for them.
What kind of return are you looking for with CRM?
|