Open Standards, SIP and SOA: Summer of Love in the Communications Market?
Avaya-Nortel: SIP Architecture Becomes Foundation for New Product Roadmap
As I listened to Avaya’s new roadmap announcement on January 19th and wondered if they made all the right decisions, I couldn’t help thinking about the complexity of an M&A process and its implications for everyone involved. This article is not about the specific product choices Avaya made, although I thought they did a good job taking multiple factors into consideration including product features and capabilities, customer and partner investment protection concerns, and vision for the evolution of the total portfolio and architecture. Extending the life of most Nortel products for another 18 to 30 months and continued support for Nortel’s more advanced and unique products such as Nortel’s AS5300 were good calls. I was surprised to see so many end users inquire about the fate of the Call Pilot and I am glad Avaya had some good news for these customers. I also thought Avaya’s decision to keep and evolve ACE was the right one as I believe ACE and application enablement will be key for its competitive positioning going forward.
It is only natural that Avaya intends to eventually merge and integrate all products and solutions into the Aura architecture. Aura is a technological framework (and not just packaging or a marketing term) based on SIP and SOA, and it makes sense for Avaya to look to integrate its now extended product line into the same vision or framework. It will be critical for Avaya to continue evolving this framework with an eye on new technological developments and customer and partner needs.
Application Enablement and Openness Drive New Competitive Dynamics
I think we should, however, look at the Avaya-Nortel acquisition from another angle as well. It provides an example of portfolio integration challenges and possibilities in the context of current technology trends towards greater openness and interoperability.
The shift to open standards, SIP and SOA is now making such acquisitions less painful than they used to be in the past – for the merging vendors, the channel partners, and their business customers. It will take Avaya less time and effort to integrate the best-of-breed applications of both vendors into its Aura framework because of the greater openness and interoperability of both vendors’ advanced communications solutions. Customers can more cost-efficiently mix and match platforms and aplications, not only from these two vendors, but from other vendors as well, since communications are becoming more software-centric and standards-based. Overall, today, customer investments are better protected and less vulnerable in case of abrupt changes in competitive dynamics.
In Avaya’s case, SIP, Aura and ACE will play key roles in delivering a more flexible and cost-effective migration path to its customers. Other vendors have their own next-generation architectures and application enablement environments that allow them to integrate with competitors’ platforms and applications. The capabilities of each vendor’s application enablement technologies vary from a more limited set designed to integrate communications with messaging and presence platforms (e.g. Avaya’s AES) to a broad range of capabilities including integrations with messaging, presence, business process, Web 2.0, mobile, and contact center applications, TV and video broadcasting, etc (e.g. Nortel’s ACE).
As unified communications become further integrated with digital content, business process applications and other, non-communication technologies enabling “contextually-rich communications” and “communications-enabled business processes (CEBP)”, vendors will need to open their solutions and create tools for customers, partners or their professional services arms to develop custom solutions addressing specific customer needs. Such tools and application enablement environments can be made available to large communities in the cloud so that multiple parties can contribute to the process of creating new applications and mashups. Some of these new mashed-up applications that can be deployed out of the box can eventually become productized to provide a more cost-efficient alternative to SMBs and a new revenue stream for vendors.
Application enablement capabilities will be key for all communications vendors going forward, but they will be even more critical for vendors providing best-of-breed solutions designed to operate in multi-vendor environments.
Of course, vendors have a long way to go before standards become truly open and customers can seamlessly, quickly and easily integrate multi-vendor applications. SIP, though touted as the communications standard of the future, in its pure form offers only a limited set of features. Entirely or partially proprietary solutions still offer better features and capabilities than most open-standard ones. Therefore, although most vendors claim SIP support, the different versions of SIP used along with the proprietary enhancements are not entirely interoperable.
Most likely, the cloud and cloud-based communications will help push further the frontiers of openness and interoperability. Instead of connecting multi-vendor applications and platforms individually at each customer’s premises, vendors can integrate more economically and on a larger scale in the cloud, delivering choice and flexibility to their customers unmatched in the premises-based world. In the beginning, many of these cloud-based services will be simple and will only offer some lowest common-denominator capabilities, but will enable some integrations out of the box, sparing customers the hassle and the cost of complex integration processes taking place in premises-based installations.
Partnerships, Alliances and M&A in a More Open Communications World
Customer demand for application integration will drive vendor efforts towards greater interoperability and co-opetition. Improving standardization and openness in communications technologies, in turn, will enable vendors to more easily engage in partnerships and alliances in order to deliver greater value to their customers.
There are multiple reasons why companies wish to merge. Most often, they are looking for new revenues streams, but also – for opportunities to more tightly integrate their technologies and deliver a one-stop shop value proposition to customers. Will more open architectures reduce the appeal of complex M&A processes in favor of partnerships and alliances? Should we expect further market concentration or the proliferation of more innovative and nimble market participants providing business customers with a wide array of options?
Power in the top tier has become concentrated, but the SMB market remains quite fragmented. While it will become less appealing to go through an M&A for the purposes of ensuring technology integration, it will also become less challenging to integrate portfolios in case of an M&A. M&A will likely take place for the purposes of acquiring installed bases, skill sets and business models (e.g. professional/managed services), simply eliminating a competitor, or for geographic expansion. I believe both trends (consolidation and fragmentation) will persist, but the drivers behind vendors’ business model decisions will change. What do you think?