Most corporate workers already spend their days using Microsoft Office. The company's goal now is to get more servers to follow suit.
With an already commanding share of the desktop market, Microsoft these days is trying to transform Office into a tool that is deeply tied into a company's core business processes. In Microsoft's ideal world, Office serves as the friendly, familiar interface for the massive databases that hold a company's customer and other information.
The server effort--which Microsoft is talking up this week at its first-ever Office System Developer Conference--helps the company in two ways. First, it helps boost sales of Office and other Microsoft server software, such as Exchange and SharePoint. But perhaps more importantly, once a company integrates Office into its practices, competitors will face a really tough sell.
News.context
What's new:
With its Office software, Microsoft more or less owns the market for word processing programs, spreadsheets and other such desktop productivity applications. Now it wants to see Office deeply tied into companies' core business processes.
Bottom line: If it can get Office into the work flow, Microsoft will boost sales not only of the productivity software but also of other Microsoft server programs, such as Exchange and SharePoint. To do that, though, it will need lots of developers churning out applications that use Office as a key component. A conference this week in Redmond assembles just the folks the company is courting.
"The chances you are going to switch out are pretty well nil," said Directions on Microsoft analyst Paul DeGroot. "You have way too much money invested."
Although Office has the majority of the productivity-software market, the company has continued to see encroachment from OpenOffice.org and other low-cost competitors--particularly in the public sector.
The first step in the effort was building XML tools into Office 2003 that let companies easily move data in and out of Excel, Word and PowerPoint. But for the effort really to take root, Microsoft needs developers to buy in to the idea and create applications that build on Office.
"It's not valuable until someone does something with it," Microsoft corporate VP Richard McAniff said of XML. "When someone builds a solution, it becomes really valuable."
Microsoft says it has made great progress, noting that the company itself has trained 70,000 partners to develop programs that sit on top of Office. Plus, a new study claims that more than 1 million people have done some software work that ties in with Office 2003, with a third using XML to do so.
But DeGroot said the company still has a ways to go if it wants to make Office a primary tool for business process integration.
"I don't know that Office is people's first option when they look at automating things," DeGroot said. Although Microsoft has a capable set of tools, including Visual Basic for Office, DeGroot said developers tend to stick with what they know. And he said the software giant still faces the dual tasks of convincing companies to automate business efforts and of selling them on a role for Office.
Topping off the bottom line
How much this effort has increased sales is unclear. Microsoft has given little information on how Office 2003 is doing, other than to say that it has outpaced sales of the prior version, Office XP. After seeing a jump in sales when the software debuted, Microsoft has watched revenue in its information worker unit level off some. Last quarter, the division had $2.78 billion in revenue, down from $2.86 billion a year earlier.
Gartner analyst Michael Silver said there is reason for optimism. Attendees at a Gartner conference in October said that on average about 8.5 percent of their machines were running Office 2003, with 50.6 percent planned by the end of 2005.
"It looks like Office XP peaked at under 30 percent, so a projection from these folks of over 50 percent is good news for Microsoft," Silver said, adding that such projections often prove overly optimistic. "Even if they get into the forties by the end of next year, that's really good."
Europeans polled at a conference in November indicated slightly lower growth, with Office 2003 representing 5 percent of the market and projected to be at 33 percent by the end of this year.
Silver said that business process integration is not at the top of the list for customers that are moving to Office 2003.
While I like the idea of MS Office becoming a development platform (I've been developing in Access and with the Outlook Object Model for years), I think MS has a way to go in giving us the tools to be sucessful.
Office is still using the JET database engine, and the version VBA included with office is still based on Visual Basic 6 (released in 1998). Moreover, documentation on items such as the outlook object model is limited and often very difficult to find.
So I say give us the "tools"! Integrate MSDE (SQL Server), and please, please update VBA to included VB.NET.
I need a clean, unencumbered word processor which can generate the basic documents I need. I want a clean spreadsheet which can track data for me. I need a basic data base to link resources. I DON'T need some bloated ou,t on-steroids, Office 'system' no matter how 'nice' Bill claims it will be.
The KISS principle is still the way to go, Focus the application designs on their core jobs. Then, as needed, develop supporting applications to go into other activities.
Integration is the route of fools. That's like trying to come up with one golf club good for any shot on the course.
A trap I've seen people fall into is developing applications in Access only to find out that the application requires a significant amount of recoding with each Access upgrade. This isn't worth the time and effort in my opinion. I've stuck to developing web based, platform independent apps only , as they seem to have a much longer life span with much less maintenance.
Apple says it's got a third-party group looking for issues at manufacturing partners it uses. Read CNET's FAQ to find out how we got here and what the next steps are.
NY professor believes that a word-based algorithm can help bring together those who believe, with one glimpse, that they have found and lost the love of their lives.
After a higher-than-expected fourth quarter, the video subscription service unburdens itself of a pending yearlong class action suit and settles for $9 million.
Along with green-lighting Google's buy of Motorola, the Justice Department today OKs an Apple-Microsoft-RIM partnership deal to buy Nortel patents, and Apple's plan to acquire Novell patents.
Chamtech's spray-on antenna uses a nano material to provide a low-power boost to antenna range. The wireless-in-a-can product may some day bring an end to unsightly cell towers.
This week, we pass around Sony's new PlayStation Vita for some hands-on testing, check out HP's newest Beats Audio laptop, and debate the best and worst Valentine's Day gadget gifts.
EnerG2 opens a plant to make an engineered carbon that will improve performance of energy storage devices and make storage for start-stop hybrid cars less expensive.
Office is still using the JET database engine, and the version VBA included with office is still based on Visual Basic 6 (released in 1998). Moreover, documentation on items such as the outlook object model is limited and often very difficult to find.
So I say give us the "tools"! Integrate MSDE (SQL Server), and please, please update VBA to included VB.NET.
Just my two cents
Tim
Boston, MA
generate the basic documents I need. I want a clean spreadsheet
which can track data for me. I need a basic data base to link
resources. I DON'T need some bloated ou,t on-steroids, Office
'system' no matter how 'nice' Bill claims it will be.
The KISS principle is still the way to go, Focus the application
designs on their core jobs. Then, as needed, develop supporting
applications to go into other activities.
Integration is the route of fools. That's like trying to come up
with one golf club good for any shot on the course.