The Challenges:

1. The single vendor fallacy

Selecting a single telecom (Avaya, Cisco, Nortel, Mitel, Siemens etc…) platform accomplishes far less to meet the goal of reducing long-term ownership costs than you would expect. Several flies appear in this well reasoned ointment including:

• Single Vendor maintenance services for the platform you choose/chose are largely an illusion. These global platform developers increasingly rely on small to medium distributors of varying and limited geographies and capabilities. You may have a support contract with the manufacturer; but at the end of the day, your staff will be coordinating and otherwise dealing with multiple service providers to cover your nationally distributed sites. To illustrate, Avaya and Siemens are pushing more tier 1 through 3 services to their partners. In a further outsourcing play, Siemens is outsourcing all field services to broader territories to a third party who traditionally relies heavily on hourly contract workers.
• An acquisition of other companies is likely to create a near instant mix of communication platforms. Your firm ends up managing at least one new platform with each firm acquired assuming the acquisition target had previously standardized its enterprise telecom platform. If the target hadn’t standardized, your telecom team is facing the need to manage and maintain multiple platforms over night.
• As manufacturers rapidly move to develop their VoIP and Unified Communications server technologies, legacy PBX systems are placed on end-of-life and end-of-support status prematurely; long before the installed systems fail to address the 95+% threshold of user needs for a technology refresh. The business case for a platform refresh is absent, yet the voice communication partner has an end-of-life gun pointed at your head.
• Managing new server-based communications technologies along with legacy systems presents similar interoperability and support challenges as managing multiple manufacturers’ platforms. Mix 2 manufactures with legacy PBX and IP-telephony systems and…you get the idea.

2. Multiplication issues

The internal support of IT/telecom systems spread across 50-100 cities compounds the management headache of coordinating service providers. Multiply the number of cities by the number of different platforms in the network and the headache becomes a migraine.

The primary challenge is not the physical distance. The primary challenge is information management. When the headquarters IT/Telecom team has scant records on the remote site, they view the distance (to go look and see, i.e. collect information while trying to fix a service affecting issue) as the challenge. If the design and other records from the original installation were maintained, the need to dispatch a tech to go, look and investigate would be less.

Consider the following recommendations to addressing these challenges:

1. Let go of the illusion of single vendor support. Call them PBX, IP-Telephony, Unified Communications solutions providers. This provides a clearer picture of just how many different communications vendors are entrenched in the firm. These vendors say their main business is developing and selling software-based solutions. The ongoing maintenance and support is being pushed out to distributors and channel partners. It is the rare customer who is supported directly by the manufacturer.
2. Equip your staff with tools that proactively manage the network, servers, and other devices. By proactively managing, I refer to:
   • Active monitoring and with the flexibility to fine tune what events represent “Majors” to your business.
   • Proactively build, manage, and maintain the design, carrier, cable, rack lay out and other information. Having this information readily available will accelerate problem resolution. The on-going management of this information is easier than trying to research for it under battle conditions.
   • Collaboration tools leverage the monitoring and information among the team members (employees, vendors and partners), streamlining the routine support and project management functions.
3. Become more independent utilizing proven tool sets that are designed to manage multiple platforms and generations of technologies.

These challenges and recommendations are often woven into the sales presentations of large IT outsourcing companies. They can hire large staff, apply best practices, and invest in tool sets. However, not all companies are willing to trust that an outsourcing play will not result in less control and personalization than can be accomplished by an internal team.

Telizent offers enterprises the tools and services needed to self service and fill the gaps of the challenges cited above.

What are your thoughts on the prospect of self maintaining your communications environment? If you found this post useful, please leave a comment, share with your peers, or subscribe to the news feed to have my future posts delivered to your news feed reader.