Home   Article Categories   Industry Events   Webcasts Surveys
Unified Communications Strategies
Community Blog
   Industry Buzz   UC Strategies Views   UC Expert Views   In The Spotlight  

Entries Tagged as 'Communication Enabled Business Processes'

New Year’s Resolutions I’d Like To See

It’s that wonderful time of the year when people around the world make their New Year’s resolutions – things they’ll do differently, bad habits they’ll quit, good habits they’ll start, and so on. Here are some New Year’s resolutions related to unified communications that I would like to see in the coming year.

Vendors working together toward federation: One of the biggest obstacles to UC success is the lack of federation, or the ability for one vendors’ UC/IM/presence offering to work with another’s. While we’ve seen some good success stories of UC helping companies internally, the number of situations where companies can use UC to interact with customers, partners, and suppliers using different platforms and different vendors’ products is limited. If I’m on a Cisco UC system, I can’t see the telephony presence of my customer on an Avaya UC system, for example. Federation is number one on my wish list.

Vendors, analysts, and consultants agreeing on a definition of unified communications: We’ve all been harping on this for a while, but there are still multiple definitions not only of UC, but also of Communication Enabled Business Processes, which is confusing to enterprise customers.

Analysts and vendors agreeing on a way to measure the UC market: As an industry analyst one of my jobs is to analyze and forecast the UC market. I’ve been an analyst for many years, analyzing several different markets – the unified communications market is by far the most difficult market I’ve had to measure. There is no agreement within the vendor community as to what constitutes the UC market, and they have not been forthcoming in providing market data that could be used in a market analysis (most likely because we’re still in the early stages of the market and the shipments have been limited).

Vendors and resellers providing sales and shipment data for their UC solutions: While PBX market analysts can easily count the number of PBX lines that have been shipped, or in the email market we can count the number of email licenses sold, there is no single element to count in the UC market. I resolve to develop a way to measure the UC market, but I need future buy-in from vendors and resellers who will need to provide the necessary market data.

Resellers being more receptive to selling UC solutions, rather than “boxes”: I know it’s a hard transition for many resellers who have been successful selling telephony or convergence products, but the time has come to embrace UC, which means a new sales approach. This approach may involve taking a vertical focus or a longer-term solution focus, but it is necessary. Some resellers are making the transition more easily than others, but vendors will be changing the way they compensate partners, so these partners will have to accept this and get on board.

My personal resolution: I resolve to be more open to other people’s definitions of UC and CEBP – this is an evolving market, and it is too early to say what it will look like in a few years. Even though I have firm ideas about what makes a UC solution, there are others with different beliefs, and many of these should be taken into account. I resolve to listen to these other ideas and integrate them into my own when appropriate.

If we as an industry can make and keep these resolutions, it will go a long way to helping the Unified Communications market grow.

Why Avaya is Differentiating CEBP From Unified Communications

I’m having lots of discussions with the Avaya folks about Communication Enabled Business Processes (CEBP) while in Boston at the Avaya Analyst Conference, and I’m finally starting to see why they’re differentiating CEBP from Unified Communications. I originally disagreed with Avaya about separating out CEBP from UC, since I (and my UCStrategies.com colleagues) believe that business process integration is a key part of UC and its value proposition. That being said, CEBP (the way Avaya defines it) is indeed different from UC. While UC is generally person triggered (an individual or worker initiates the communication), CEBP is event triggered (a business process-related event initiates the communication). The event could be an inventory shortage, a stock price change by a specific percentage, a manufacturing malfunction, a shipment delay, etc.

 

I’m thinking that instead of calling it CEBP, it should be called Automatic CEBP (ACEBP), since the key is to have the events automatically trigger the communications related to the business process. Rather than having an individual identify a problem or situation and initiate a phone call, conference call, web conference, etc., a specific event automatically generates the notification and communication with the appropriate parties. This may or may not include presence and UC capabilities.

 

So this really comes down to semantics – CEBP, the way it’s defined by Avaya and others, is indeed different and separate from UC. I still have some problems with the term Communication-Enabled Business Process since Unified Communications is optimized when comm-enabling business processes and applications. The difference is that CEBP does this automatically based on an event trigger.

 

I’ll be having lots more conversations with Avaya about CEBP and UC over the next couple days, so stay tuned.