Telco 2.0 - the Microsoft way

The following are comments from Ovum SVP, Brett Azuma on Microsoft and what they are up to in service provider communications. I thought this was worth passing along.

Microsoft provided an update on its Telco 2.0 vision. The analyst telebriefing indicated that Microsoft's revenues for the Communications Sector exceeded $2bn in 2007. This includes everything that Microsoft sells to service providers including software and services that the operators use to run their internal businesses, which account for the overwhelming portion of the revenue. Microsoft segments its Communications sector business between software and services sold to the service providers and those sold with them. Microsoft's approach for the latter category is a combination of telco and Microsoft hosted services aimed at the enterprise and consumer markets. Microsoft currently has over 40 deployments of the Microsoft Connected Services Framework (CSF), a service aggregation platform, with the majority of those operators providing commercial services.

"The revenue share price model is a good way to remove much of the financial risk in deploying new services."

"The Sandbox was announced a little over a year ago. The open question is why there are only 2,000 developers currently involved. Two of the possible conclusions one can draw are that ISVs see communications as a limited opportunity or that the tools and technology are too hard to leverage. These conclusions have significant impact on the pace at which this market will develop."

Full commentary below:

"Microsoft laid out a cogent set of services for both the SME and consumer markets. While some of the target ARPU numbers were a bit generous, it does point to a set of attractive services for the operators to offer. The price model is a revenue share which is a good way to remove much of the financial risk in deploying new services. While Microsoft claims integration of its solutions as a key differentiator, there appears to be nothing across all of the services which gives them bundling leverage except price. This is good for operators, but it reduces Microsoft's opportunity to dominate this market.

Additionally, it has positioned its ecosystem to enable ISVs and Developers to migrate their offerings into SaaS applications. It is a three-step program which includes upfront discount licensing and architectural guidance to incubation centers and finally into the CS Sandbox. The CS (Connected Services) Sandbox is a program and online facility to enable ISVs, SIs, service providers, and application developers to test new services and integrate them with web services available from Microsoft and other participants. We have seen a number of other initiatives within operators to also reach out to ISVs including, BT's service oriented infrastructure and AT&T via its SaaS agreement with SAP.

Microsoft announced that over 2,000 developers have started to work with the CS Sandbox. The purpose of the sandbox is to provide a live proving ground for service mashups. The company believes that mashups will be an important source of service innovation going forward. Development and testing sandboxes have become quite popular among vendors trying to build development communities. With over 70,000 ISVs and 6.5m developers, the group of developers participating in the Microsoft CS Sandbox remains a small portion of their developer community. The Sandbox was announced a little over a year ago. The open question is why there are only 2,000 developers currently involved. Two of the possible conclusions one can draw are that ISVs see communications as a limited opportunity or that the tools and technology are too hard to leverage. These conclusions have significant impact on the pace at which this market will develop.

Microsoft has done much to build a strong support program to help the operators ranging from aggressive licensing terms to co-marketing programs. While helping the operators to start offering new services is key to get things going, this represents the back-end of the innovation pipeline. The front end is the application developers that will feed much of the innovation to the industry. In addition to providing technical support, Microsoft will need to go the next step to help these developers commercialize their offerings in order to create a sustainable development model."
| 0 Comments | 0 TrackBacks

Listed below are links to sites that reference Telco 2.0 - the Microsoft way:

0 TrackBacks

Telco 2.0 - the Microsoft way TrackBack URL : http://blog.tmcnet.com/mt/mt-tb.cgi/35117

Leave comment to Telco 2.0 - the Microsoft way article

Subscribe to Blog

October 2008

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

About this Entry

This page contains a single entry by Rich Tehrani published on February 14, 2008 2:29 PM.

Verizon's Network Upgrades was the previous entry in this blog.

Corporate Phone Bills: $133 Billion in 2008 is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Yearly Archives

'04 '05 '06 '07 '08
  Jan Jan Jan Jan
  Feb Feb Feb Feb
  Mar Mar Mar Mar
Apr Apr Apr Apr Apr
May May May May May
Jun Jun Jun Jun Jun
Jul Jul Jul Jul Jul
Aug Aug Aug Aug Aug
Sep Sep Sep Sep Sep
Oct Oct Oct Oct Oct
Nov Nov Nov Nov  
Dec Dec Dec Dec  

Around TMCnet Blogs

Latest Whitepapers