A lot has played out in the UC world over the last couple months and I think it’s time to revisit the question of “What is UC?” and dive a little deeper. In this series of posts I’ll analyze what functional components make up a UC solution and examine offerings from IBM, Cisco, Microsoft and others.
Since the paragraph above is really just a tease on its own, I’ll dive right into an overview of Unified Communications. First, a disclaimer that UC seems to mean something different to each company. This is my opinion based on talking with a LOT of customers and doing a few dozen rollouts. It’s certainly not the only opinion however.
The 2007 Gartner report on UC states:
In a way, identifying who’s doing what in the UC industry is a little premature, because, until the new technologies are really finished or legacy technology is really ready to be replaced, UC has to be viewed as “a migratory work in progress.” However, it is important to track technology developments, products, and services so that IT will be ready to selectively deliver new UC capabilities whenever required.
I’ll start by saying there are two sides to unified communications; well at least two. First is functional, ie. what functions are included under the UC umbrella. The second is a business culture shift, ie. changing the way you to do business to take advantage of UC through communications enabled business processes (CEBP). In this post I’m going to speak more to the first. I’ve done a lot of research on the second only to conclude that the business case, and ROI plan, is vastly different for different companies and users. Thus, it needs to be addressed individually. Beyond recouping conferencing costs from bringing the function in house, the ROI model gets very complex.
Although I’m happy to discuss individual cases on a one-off basis I want to keep the topic of this post more generic. I’ll be focusing on the functional aspects of UC that apply to most, if not all, companies.
So, if we believe in the assumption that, from a functional perspective, UC is a platform not a product we must ask what are the parts of that platform? Here’s my take on what every UC platform needs:
Presence engine - A service or function that shows a person’s availability and willingness to communicate over multiple modes of communication. Features include:
· Contextual presence – willingness to communicate over multiple modes of communication (text, voice, video) depending on access and availability
· Integrated presence – Pulls information from other sources (calendar, phone) to automatically update states of presence
· Multi-tiered presence – user-defined levels of access for presence visibility
· Deep presence – More levels than online, offline, away
Instant Messaging - The ability to send text messages and files in one-to-one and many-to-many communication. The features include:
· IM in real-time with others
· Transfer files during a chat
· Escalate IM conversations to richer communication (voice, video, ad hoc web conference)
· IM in a group, more than one-to-one
Federation – The ability to search and communicate across security boundaries, like between partners, in a secure manner.
Public IM – The ability to communicate with popular public IM providers. I never thought this was an absolute requirement but it’s been in every requirements document I’ve seen lately. People are used to IMing and don’t want multiple clients regardless of who they’re communicating with, business or personal.
Audio and Video Conferencing from a desktop client – Normally 2 distinct requirements I never see one without the other so I’m bunching them together. I’m speaking purely PC-to-PC or PC-ConferenceRoom here, not yet into IP Telephony.
Web Conferencing - the ability to host scheduled and ad-hoc meetings including voice, video, data and shared desktop collaboration
· Ad hoc and scheduled web conferences including internal and external participants
· Shared documents and “handout” functionality
· Shared desktop for collaboration
· Support data, voice and video conferencing during meeting
· One-to-many live video streaming (ie. virtual company meeting)
Messaging Platform – A robust enterprise email and calendaring platform. Email has surpassed voice as communication mediums go so it needs to be scalable and reliable.
Mobility – The platform needs to have a mobile client for syncing mail and calendaring as well as IM/presence and other UC modalities.
Collaboration – Some would argue that a collaboration platform should be its own topic. And well it could be, but I feel any UC solution needs to have a strong collaboration story. After all, UC is all about collaboration. Once you find a person and IM them, where are you going to work together?
Extensible API – As I mentioned above, UC means something different to everyone. An extensible API is an often overlooked requirement for extending UC functionality into other applications.
IP Telephony – Often just called VoIP, a UC solution needs basic IPT functions like single number reach, unified messaging (voicemail in email), and click to call. These functions need to be in the same UC client as other functions (IM, etc). No one wants 4-5 clients running to accomplish one communication task.