Speaking directly to the 2005 infrastructure consolidation, which is really what we're here to talk about, I think, to be fair, there were a number of motives.
Clearly, we had been watching what hits.... Hewlett-Packard was kind of the poster child from this perspective, but IBM was there as well, and we certainly learned a lot from both IBM and HP.
I think there was a realization of what the potential could be, from a service perspective. When you're managing a single set of infrastructure as opposed to multiples, you can react more quickly and you can do things much more efficiently and much more effectively. You can ally your clusters. In other words, you can ally your IT people who are involved with the business to focus a lot more on providing the higher-end types of services, such as application development, advice, strategic planning, or information management. You can really shift your focus of work away from worrying about a desktop or a laptop or a BlackBerry or an e-mail account, and start thinking about things that really matter to citizens and to businesses.
I think the mantra was very much about that service element. There's no doubt that the cost savings were attractive as well, but honestly, in this case, one really does go with the other. There's no excuse for it not to; you really can increase services and you really can save money.