Commentary

Eric Krapf
Editor  

Mystery And Margin

Over at No Jitter, consultant Gary Audin has posted a blog based on a new report that looks at IT services costs. The report, from the OnForce analyst firm, finds that VoIP is by far the most expensive IT component to service; the average VoIP work order is more than half again as expensive as the next-highest category, wiring and cabling, which of course also can be a significant contributor to VoIP/IP telephony expense, too.

Over at No Jitter, consultant Gary Audin has posted a blog based on a new report that looks at IT services costs. The report, from the OnForce analyst firm, finds that VoIP is by far the most expensive IT component to service; the average VoIP work order is more than half again as expensive as the next-highest category, wiring and cabling, which of course also can be a significant contributor to VoIP/IP telephony expense, too.OnForce attributes VoIP/IP telephony's higher maintenance cost to its relative youth as a technology. In the report, it writes:

We're not at all surprised to see VoIP at the top of this list as the most expensive IT service category, given that it's an emerging technology compared to established categories like Networking and Computers. In our conversations with VARs and solution providers, this is attributed to the idea that "where there's mystery, there's margin."

More Telecom Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This perspective jibes with some data that Robin Gareiss of Nemertes Research presented in a recent VoiceCon Webinar. Nemertes's survey of enterprises found that the typical enterprise's telephony troubleshooting/problem isolation costs actually will increase by 26% in the first 12 to 24 months of an IP telephony deployment. On the other hand, costs for "moves, adds and changes, software updates, routine maintenance of PBX, phones, monitoring" typically fell by 24%, mitigating the higher troubleshooting cost.

Troubleshooting IP telephony will probably always be more involved than the legacy TDM systems made it, because when you have a problem with an IP telephony system, you don't just have to look at the PBX, the phone, and the line between them. The problem that's causing bad quality or dropped calls, or whatever, could be in none of those places; rather, it could be in the IP network -- any number of things could be degrading network quality, so multiple teams might have to get involved in finding the answer. As Nemertes' data suggests, this should shake out within a couple of years, as IT staffs develop troubleshooting routines and, probably, add management tools, that isolate problems more quickly and efficiently.

But this is an element that has to be taken into account when calculating the ROI for IP telephony. On the one hand, there are quick savings to be had from IP telephony, especially if your enterprise does a lot of audio conferencing or has a big international component to its voice traffic. The latter can be a double savings -- not only can you put international voice traffic on IP trunks and save expensive PSTN charges, but an increasingly important -- and often hidden -- cost hits enterprises in the form of international cellular roaming charges for employees who travel abroad. Several enterprises have spoken at VoiceCon about their decision to press internationally-mobile employees to implement softphones on their laptops, so that when they travel overseas, they can do their calling on the enterprise VPN and save those roaming charges, at least when they're calling from their hotel or remote offices.

The flip side of the cost savings is that, as the OnForce report states, the technology brings mysteries to your IT picture, which means either margin for your IT services provider or costs for your internal staff. This shouldn't be overlooked when calculating the cost of IP telephony.

And if you think there's mystery with basic VoIP, just wait until you get to full-blown Unified Communications.


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