Beyond Vista
- 22 January, 2007 12:19
Reader ROI
- What tools Microsoft believes CIOs will need in a future built on Web services
- How it plans to provide those tools
- Where Microsoft will fit into the CIO's IT strategy going forward
Every decade or so, a new platform emerges that reduces the cost of running an IT department to such an extent that vendors have no choice but to embrace it or die. In the 1990s, PCs with powerful operating systems spelled the end of mainframe development and ushered in the client/server era. Today, cheap servers and high-speed Internet connections are triggering a move away from traditional desktop PC software and to software as a service, hosted by a third party and delivered over the Internet.
No company has as much to lose from this shift as Microsoft, which dominated the client/server era on the strength of its Windows operating system. Microsoft is currently enjoying a moment in the spotlight thanks to Vista (the latest version of Windows), the fruit of five-plus years of development and what Microsoft COO Kevin Turner calls the "biggest R&D investment in the history of Microsoft and arguably the history of business". But Vista isn't a part of the software-as-a-service trend, and all the pomp and circumstance around its release mask a growing concern inside the company, one that comes through in executives' demeanour, internal communications and candid conversations about what the IT world will look like five years from now: Software as a service is a threat unlike any the company has faced before, and Microsoft must make dramatic changes if it wants to remain the most important technology company in the world.
To Microsoft's way of thinking, the Web services world will make a CIO's life messy and difficult
To Microsoft's way of thinking, the Web services world will make a CIO's life messy and difficult. While each software service that a company subscribes to will be cheaper and easier to operate than its client/server counterpart, collectively they will make the enterprise exponentially more complicated, unless CIOs have tools to provision and manage those services as a suite. Microsoft vows to develop those management tools and make them the centrepiece of its enterprise business.
Once those tools are built and deployed, Microsoft says, it won't matter if the applications an IT department supports are Web-based services hosted by an outside party, client/server software hosted internally, or a combination of the two. "[CIOs] have to have a way of provisioning an account, providing the initial connection and user interface", regardless of an application's source, says Ballmer. "At least that's our vision."
But even Ballmer admits that right now, a vision is all it is. Microsoft has accepted and internalized the idea that the software market has shifted ineluctably to services, and the company has seen there a critical opportunity to move forward. But to succeed, analysts say, to change its corporate strategy, identity and DNA, Microsoft must overcome equally critical barriers of technology, strategy and culture.
Where Microsoft Sees Its Opportunity
The widely preached gospel of software as a service says that companies willing to give up the control that comes from running an application internally will save money by not having to maintain and host those applications and, by freeing up those resources, will become more agile and productive. CIOs running services, the gospel goes, don't have to buy and operate farms of servers or trudge from desktop to desktop upgrading software. Instead of a model that encourages long, costly upgrade cycles (the very model upon which Microsoft built its enterprise empire), software as a service allows for small, steady, incremental improvements. That's just one reason it could kill CIOs' appetites for traditional client/server software like Microsoft's.
Furthermore, all a user needs to access a Web-based application is a browser — not a robust operating system tightly integrated with the application. Therefore, unlike in its past battles with Netscape and others, Microsoft cannot rely on its Windows strength to pull its bacon out of the fire. And while Microsoft argues compellingly that it would be foolish not to take advantage of all the processing power a PC offers, the company simultaneously is planning for a future that will rely upon less powerful mobile computing devices and ubiquitous high-speed Internet connections.
Page Break
The hard truth is that Microsoft has no choice but to confront software as a service. But rather than fighting it, Microsoft looked for an opportunity. And, it says, found one.
"Some people say that [software as a service] is a panacea and that everybody should immediately switch off everything they have and go to this world," says Andy Lees, VP of Microsoft's server and tools marketing, his sarcasm foreshadowing what comes next. "But here's a problem with it: The first service that you have is beautiful, the second service that you have is kind of nice; from then on you have all of the same problems that you had before."
In other words, the CIO still needs to manage a lot of applications. It's just that this time the applications are hosted somewhere else. It's a problem that CIOs are aware of, even if the conventional wisdom (and enthusiasm) surrounding software as a service often ignores it.
"Managing multiple services applications — as well as the things you run yourself — is going to be a challenge," says Joseph Devenuto, CIO of Norton Healthcare, a hospital chain in Kentucky. "You're looking at a world of headaches."
When someone leaves a company (for dramatic purposes let's say a disgruntled accounts payable clerk is fired for gross misconduct), instead of deleting her account from the internal systems, a CIO in a services environment would need to make sure that all the software providers — everything from e-mail to CRM — make the change in their systems, Lees says. Since the disgruntled ex-employee can access the hosted applications through a browser on any device, the risks multiply.
"Quick, get all the IT guys and dial in to those six, seven, 15 different systems that you no longer own," says Lees.
Obviously, you can do that, says Ballmer, but the problem is that doing so will devour a disproportionate amount of time and resources. Microsoft's vision is to come up with products and services that allow CIOs to manage Web applications — as well as internal client/server ones — from a single place. In addition to providing a central place for provisioning, Microsoft, according to Lees, will let CIOs set rules and enforce policies — for example, all orders must be processed by 3:30 in the afternoon. And workflow features will help CIOs automatically manage exceptions, he adds. Today's CIOs "spend all their time configuring and changing and monitoring", Lees says.
"[CIOs] feel like cost and complexity weigh them down," says Ballmer. "I want to make sure we're eliminating that cost and complexity and letting them focus on taking advantage of new innovations and things that can add value to the company."
What's the Answer? Steve? Kevin? Ray?
Microsoft is a product company, and for the past decade its Windows and Office products have stood head and shoulders above all others. Historically, those two business units have been responsible for almost all of the company's earnings. However, that's changed over the past several years. Revenue for Windows and Office has remained relatively flat, while the server and tools division has posted double-digit revenue growth for 16 straight quarters. Today, the server and tools division is almost as large as the veteran groups — generating 22 percent of Microsoft's $US44 billion in revenue, compared with 29 percent and 25 percent for the Windows and Office business units respectively.
If the company is going to reinvent its enterprise business around one of its units, this is the one to pick, says Rick Sherlund, an analyst who covers Microsoft for Goldman Sachs.
But creating tools that allow CIOs to manage, configure and provision a suite of disparate applications is both a technical and strategic challenge. And no one, inside the company or out, can articulate exactly how Microsoft is going to get there.
Ballmer says that Microsoft has many of the tools in place but that they are "certainly not anywhere close to sufficient", adding that "no one product is this vision." However, he believes that Microsoft has the right combination of enterprise and Web experience to pull it off. Oracle and SAP, he argues, have a scope limited to their suite of products. IBM has reinvented itself around consulting services. No other company besides Microsoft, says Ballmer, combines as much enterprise and Web experience with a rich understanding of business process.
Analysts, however, say Microsoft's competitive position may not be as strong as Ballmer describes. For starters, managing a customer's computing resources is something that Microsoft has historically left up to partners. "They have to piece about moving toward managing services," says John Rymer, an analyst at Forrester Research. Microsoft knows how to help CIOs manage its own products, but incorporating other companies' products is a substantial leap, Rymer says.
Page Break
The biggest leap, without a doubt, is that Microsoft's vision requires it to embrace a heterogeneous computing environment. Yet Microsoft executives, historically averse to working with anything they haven't built themselves, seem united in their commitment to supporting non-Microsoft technology.
"We want to do it whether you're developing [applications] or whether you're consuming them, and whether we're delivering them or whether someone else is [delivering] them for you," says Lees.
One factor could make Microsoft's work supporting this plethora of applications easier: Software-as-a-service applications all have the same delivery mechanism — the Internet — which requires that they be built with a specific set of standards. These standards — XML, SOAP, WSDL and UDDI — are the same ones that Microsoft and IBM helped push through standards organizations like the W3C and Oasis at the beginning of the decade. (For the history of the standards process, see "The Battle for Web Services.") Microsoft will have an easier time using these standard protocols to integrate with Web-based services than it would integrating with a more traditional client/server application that uses a proprietary standard, says Dwight Davis, an analyst with Ovum Summit.
There's probably a market for Microsoft's vision, says Dave Girouard, general manager of arch rival Google's enterprise division — and it may not be that difficult to achieve, since software-as-a-service providers are going to want their applications to work with a CIO's existing infrastructure. But provisioning and single sign-on are one thing; deeper integration, like porting data from an online CRM system into a legacy ERP package, will be complicated, promises Girouard.
And in the end, superficial integration will not be enough to charm CIOs. The reason that companies will adopt a particular software as a service is that its features are a good fit, says Roger Kay, president of consultancy Endpoint Technologies. Giving CIOs a single place where they can manage their software services is a great idea — but only as long as the management interface preserves the array of features that drove a company to choose a particular software service in the first place, Kay says.
Can Microsoft truly make all sorts of Web applications communicate well and play nicely?
"That's really ambitious," says Kay, noting that Microsoft will have to interact with all kinds of proprietary file formats. "It doesn't mean that they can't do it, but it will be hard."
If Microsoft really wants to be the vendor that companies turn to for managing their IT assets, it will have to learn how to support, well, all of a company's IT assets. "They have to be willing to go cross-platform, and historically Microsoft hasn't been willing to do that," says Goldman Sachs's Sherlund. "It's a bold strategy that will require broad support of other platforms and knowledge of other systems."
At the moment, all Microsoft is offering is talk. But at least it's talk that CIOs already using open source want to hear.
"The reality of the world is a lot of companies are built through acquisition," says Ron Markezich, Microsoft's CIO. "As you build through acquisition you have a lot of different platforms, and the CIO doesn't always have the power or the budget to standardize." Markezich says that it will be up to Microsoft to learn how to work with the other systems. "Take open source," he says. "We interact with it now, but it's difficult. But it's something we have to do."
For a Microsoft executive, using "open source" in a sentence without an introductory pejorative is the first step in what promises to be a multiyear struggle.
Can They Pull It Off?
Putting the technology challenges aside, there are other reasons to doubt Microsoft's ability to execute its vision. "Their approach has always been 'put in our stuff'," says Forrester's Rymer. Changing that will require a large cultural shift for a company that has more than 71,000 employees and is about to lose its guiding visionary, now that chairman and cofounder Bill Gates announced in June that he will leave the company in 2008.
Another challenge is this cultural shift will have to take place at the same time the company is marketing Vista and Office, two products only tangentially related to Microsoft's long-term strategy. Over the next year-plus, it's unlikely that a CIO will be able to turn on a TV or read a magazine without seeing an advertisement for Office or Vista. This will keep the company's marketing and sales organizations squarely focused on the company's old product-oriented business model. In fact, for all the talk about the Live initiative in the business and IT press, trying to find out about it from Microsoft's sales department is very difficult. Barbara Gordon, Microsoft's VP of enterprise sales, says she doesn't sell 'Live' anything and doesn't know when her organization will. They're focused on selling Vista.
Page Break
Customers see this reality too. "I don't think that Vista is the link between the current environment and the Web services one," says Norton Healthcare's Devenuto, who has been beta-testing Vista for Microsoft. It's a more secure operating system, he says, "not a transitional tool."
And, while reinventing its enterprise line, Microsoft is taking on Google and Yahoo for consumer applications, and Sony and Apple for consumer devices — game consoles and music players. "If I were a CIO I would wonder if the investment in MSN and Xbox is a distraction that will not allow them to deliver [on their enterprise strategy]," says David Yoffie, a professor at Harvard Business School. "Any company, no matter how large, has a limited number of A teams. Do you put that team on search or Xbox or the vision that you described?"
Microsoft counters that it doesn't comment on the makeup of its project teams but that the number of people working on the software-as-a-service management tool will increase as Vista and Office development efforts wind down.
But even if it is able to redirect significant energy to the enterprise, the new vision requires that the company move outside of its traditional comfort zone.
"Microsoft's management offerings [such as the Microsoft Management Console and Active Directory] — have historically been spotty," says Davis, the Ovum Summit analyst. "So it doesn't arrive at the table with any overarching credibility."
Microsoft's executives are all saying more or less the same things about the company's need to embrace a heterogeneous IT environment and the opportunity that managing software as a service presents. That has to continue for Microsoft to reinvent itself. "Talking the talk is step one when you are trying to change culture," says Laraine Rodgers, a change management consultant.
But while Microsoft's executives are preaching the gospel, their language sometimes betrays the company's famously closed culture. Lees, for example, introduced the concept of supporting applications built on non-Microsoft platforms by saying that's "what's called interoperable", as if no one in the room had ever heard the term before. Slips like this demonstrate just how large a change Microsoft is trying to make.
Ozzie, the man replacing Gates as the chief visionary, says supporting a Web services environment is just a logical extension of the expertise Microsoft developed in the client/server era. And at the end of the day, Ozzie says, the same skill set that made Microsoft the most important vendor then — an understanding of business issues like security, manageability and compliance, as well as its experience with development tools like .Net — will prove to be the most important factors in the software-as-a-service world.
Microsoft has the experience to build the tools that will make the services era manageable, he says. "It's unsexy," Ozzie says, "but it's what's going to make [hosted] services as important as technologies inside the data centre are today."
Page Break
SIDEBAR: The Big Upgrade
by Ben Worthen
Vista's flexibility should appeal to CIOs with smaller staffs, but its hardware requirements will be tough on their wallets
Now that the marketing onslaught for Microsoft's new Vista operating system has begun, mid-market CIOs will have to present upgrade plans to CEOs — many of whom will probably get their information about Vista from the aforementioned marketing. CIOs who've been beta testing the new OS say you'll like the security improvements, but you'll want to roll out slowly for reasons that include Vista's beefier system requirements.
Past versions of Windows made control over desktop settings an all-or-nothing proposition, but Vista lets CIOs give users more freedom by treating each configurable element differently. CIOs can, for example, give users permission to change the system clock time but prohibit them from loading information through USB drives. This flexibility should particularly appeal to mid-market CIOs with smaller and more time-pressed IT support staffs. So should the security improvements, including a myriad of fixes to XP holes and bugs, and a new feature called Bit Locker, which encrypts local files and makes it harder to access data on a stolen or lost laptop.
In Microsoft's estimation, companies currently standardized on Windows XP can reduce IT labour and support costs $US35 per PC by moving to Vista and around $US340 per PC by upgrading to all the Vista-related infrastructure products (including firewalls and Active Directory). But it's unlikely mid-market companies will be able to do either because of the new operating system's hardware requirements. Microsoft advises enterprise customers to run Vista on computers with at least 40GB of storage, 1GB of memory and a 1GHz 32- or 64-bit processor — meaning that most mid-market companies will have to buy brand-new computers in order to support it.
"We can't replace every desktop," says Joseph Devenuto, CIO of Norton Healthcare, a $US1 billion hospital chain in Kentucky. So Devenuto will upgrade to Vista on his normal technology refresh cycle, which covers about 25 percent of his 5000 machines a year. Microsoft's Brad Goldberg, a general manager in the Windows division, suggests that mid-market CIOs doing phased-in rollouts start with laptops, since the security benefits will be felt the most by mobile users.
Devenuto has one other concern. "The look and feel of Vista is different," he says. That means that mid-market CIOs could end up with one additional expense that they hadn't counted on: training.
"You'll need at least an hour to teach people the intuitiveness of it," he says.
Page Break
SIDEBAR: Now Comes the Hard Part
by Ben Worthen
To provide products and services that will help CIOs manage disparate Web apps, Microsoft must overcome at least three serious technological challenges
1. Building management tools. Microsoft isn't known for providing management tools, says John Rymer, an analyst at Forrester Research. Right now it leaves that to partners like Amberpoint. "[Microsoft] has products that let you manage Microsoft servers," says Rymer, "but I dare say that if you talked to the 10 IT shops that are using it, they would say it was for the development tools — not management."
2. Supporting applications built on non-Microsoft platforms. Microsoft has promoted some open standards around XML and Web services, says Rick Sherlund, an analyst who covers the company for Goldman Sachs, but actually supporting applications built on non-Microsoft platforms isn't something that the software giant has done. "I hear them say [Microsoft's future enterprise environment] will be heterogeneous, and maybe there are things they can do to help people to bridge that environment," says Sherlund, "but we haven't seen the pieces of that." One place to look for clues as to whether Microsoft is making progress working with cross-platform technology is in its Longhorn server, which is slated to be released by the end of 2007.
3. Preserving the unique features of services while integrating them. Companies will choose one software service over another based on features. Microsoft's challenge will be developing technology to work as a common interface with these applications without eliminating some of the more specialized features, says Roger Kay, president of consultancy Endpoint Technologies. That will require Microsoft to develop technology that interacts with all sorts of file formats. And if it can't deliver," Why would you bother with it?" he asks.
Page Break
SIDEBAR: The Web 2.0 World According to Ozzie
by Ben Worthen
We asked Microsoft Chief Software Architect Ray Ozzie: Besides managing the use of disparate Web services, what other challenges will CIOs face in the new era of software as a service?
Ozzie cites two big hurdles: Building composite apps and managing trust boundaries between Web apps.
"We've talked about composite apps as an industry for years, and it's finally really happening. We've been talking about XML and Web services for a long time . . . and people are finally using those technologies to weave together systems both within the data centre and with partners," Ozzie says.
"At the scripting level . . . mash-ups and page-level composition have proven to be quite useful. Even though it's not deep, it's really easy, and you can get things together very quickly, so that's very powerful. And at the end user level, individuals are bringing together a number of different things that are useful to them in terms of small services, whether inside or outside. You can almost think of this as business intelligence for the masses, and we feel that there's a huge opportunity within Office, at that level, to help people weave together multiple services.
"In terms of managing trust boundaries, one of the huge challenges that enterprises are going to have is . . . managing trust between components of composite applications. In a services world, if you have a service and you want to incorporate a partner's composite, a component of that service, it's very easy to just give them a password and a URL and they have access to all your internal data.
"We believe there should be significant auditing within service components — such that when you do expose a partner to certain enterprise data . . . you have a complete record of the kinds of things that their app did."
