Commentary

Eric Krapf
Editor  

Avaya-Nortel: The Pushback

Any big combination, whether it's a merger or an acquisition, is tough to pull off--tough, but not impossible.

As we count down to the September 11 bankruptcy court auction that will determine the buyer of Nortel Enterprise Solutions, No Jitter recently ran a compelling and controversial writeup from an industry observer arguing against the likelihood of a successful combination should Avaya capture Nortel in the auction. The piece drew quite a few detailed and insightful comments, as well as at least one point-by-point rebuttal on another blog.The next issue that bubbled up around the deal had to do with whether it should even pass anti-trust muster. Opponents of the deal asserted that if Avaya got its hands on Nortel, the result would be an Avaya-Cisco duopoly controlling as much as 75% of the market. My conclusion was that the business communications equipment market as a whole would not be unacceptably concentrated by such an acquisition, but Allan Sulkin and others have made the legitimate point that the North American high-end enterprise market-the very largest systems-almost surely would be heavily dominated by Avaya and Cisco, Which they pretty much are already, even without Avaya acquiring Nortel.

This issue hangs on the question of how you regulate market concentration in rapidly evolving markets. Avaya and Cisco may be the two biggest choices for the largest domestic enterprises today, but does the potential for more aggressive North American market entry from Siemens and Alcatel-two legitimate, globally dominant players in this customer size segment-offset the fact that their current market shares here are modest? Does the entry of Microsoft as a direct competitor-even though it, too, has very small market share right now-provide enough of a competitive prod to the leaders in installed base and current shipments? Certainly no one could argue that these other competitors are tiny upstarts whose efforts could easily be squashed by the big, bad Avaya-Cisco tag team.


More Telecom Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The most obvious analogy to reach for would be the RBOC mergers of the 1990s and early 2000s. In nobody's imagination could these acquisitions be seen as anything other than extreme concentration of a market narrowly defined as "wireline public telephony." Yet the deals were allowed to go through in large part because of the belief that a new sort of competition, with new sorts of players, was emerging. It was thought that the new dynamics of the new market made hitherto-unthinkable combinations a reasonable step toward the new future that was emerging.

The fact that these giant mergers were allowed will be taken by some as a reason to accept the same type of deal in the large-enterprise CPE market; while others will point to the very limited state of competition and choice that remains in the carrier industry, and see the history of that regulatory regime as a cautionary tale whose repetition is to be avoided.

Ultimately, much of the duopoly talk seemed more focused on the channel than the end customer-though the very highest end is also where direct sales are most common. To me it's also debatable whether there's any reason to split the high end off from the total market for the purposes of anti-trust consideration.

Going back to the prospects for success if Avaya does get the deal done: Any big combination, whether it's a merger or an acquisition, is tough to pull off--tough, but not impossible. It's kind of like, say, Laurel and Hardy dancing to the Gap Band: Sounds improbable, but there's always the chance it'll turn out better than you'd think:

Any big combination, whether it's a merger or an acquisition, is tough to pull off--tough, but not impossible.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links