Saturday, May 05, 2012
Video Conferencing Moves Out With UC
Sunday, April 22, 2012
AT&T Pushing Mobile Users To Their Public, Unified Messaging “Cloud”
Friday, April 20, 2012
Business Collaboration Really Means UC Enablement
Do People Who Collaborate Need Identical Devices?
The Implementation Bottom Line for IT management, Solution Integrators, and Channels
For more insights on UC-enabled Collaboration go to CIO Collaboration Network
Sunday, April 01, 2012
Avoiding "Angry" Business Messaging In A UC World
March 31,2012
By Art Rosenberg
It is not just nice to communicate with people in any business activity, but it is even more important to communicate effectively and avoid damaging relationships because of careless communications. I was intrigued by a recent announcement of a book by Dona Young, a teacher and writing coach, entitled “Angry E-Mail; How To Put A Lid On It” because it was focused on business communications. I offered to review it because I wanted to see how the recommendations fit into a UC enabled environment.
Young’s practical approach to business email begins with making sure to immediately detail the purpose of the message at the start. Recipients of business email don’t have time for socializing small talk. After composing the message, Young recommends spending a few minutes editing it, to make the purpose very clear to the recipient(s) at a glance. Then cut out all the unnecessary information because “We’re living in a world that’s moving at warp speed. One of the things that irritates people is getting an email and then having to work really hard to figure out how to respond.”
Young’s book focuses heavily on message content, tone, and style that will not offend the recipient and will elicit a positive response. However she does stress the importance of “micromessages,” i.e., things that are unsaid in the message and any excessive delays in the response. All of these factors can impact the business relationship between the sender and the recipient of the message.
Although the book covers best practices for using email to communicate person-to-person, there is no mention of other forms of messaging technologies, including business social networking, or automated CEBP contacts. However, it does suggest that a phone call for a voice conversation may be more appropriate than an email message when delivering sensitive information. The role of email in a unified communications enabled environment is something that was not addressed, e.g., “click-to-call/chat” in response to an email message. In fact, Young recommends delaying sending an email response in order to insure that the response is well thought out.
So, perhaps Dona Young’s next book should be “Angry Unified Communications!”
Monday, March 26, 2012
UC Enabled Apps Need "TCU"
Copyright © 2012 The Unified-View, All Rights Reserved Worldwide
March 26, 2012
Will Cloud Services and Analytics Shift UC “TCO” To “TCU” and “TCS?”
By Art Rosenberg, The Unified-View/ UC Strategies Expert
Voice and video communications are joining automated business applications in becoming software rather than hardware dependent. This will facilitate the interoperability and integration of these two groups of computer applications, particularly in a virtual, “cloud” based network environment that will support both desktop and mobile apps.
The transition to hosted services and BYOD mobile devices (smartphones, tablets) will shift the emphasis of technology implementation planning factors from TCO (Total Cost of Ownership), most applicable to acquisition and maintenance of premise-based hardware and software applications, to hosted and managed application service offerings.
While ROI (Return On Investment) is still an overall practical measure of benefits from any technology investment cost, those costs really should be correlated with different types of benefits that have have to expensed. Going to separate levels of benefits and related costs will make it easier to determine how applications can be used most cost effectively and how usage needs should be supported cost efficiently.
New analytics are becoming key tools for tracking application activity that will enable better understanding about who uses what applications, when, and with what results. Analytics can also provide immediate feedback on how well the application is designed from a user interface perspective, as well as indications of workforce performance in using applications by internal staff for their different job responsibilities (“roles”). While the contact center is an ideal target for analytics, it can be applied to everyone in an informational workforce environment.
Total Cost of Usage (TCU)
Probably the most logical metric that should be applied to any application or combination of applications is what I would call “Total Cost of Usage.” The amount of actual usage for any communication of business application is a measure of value for a particular application. Usage analytics will also provide feedback about who (type of user) may be getting the most value from that application; that information provides further insight into the value that application generates for a particular business process.
Putting those factors together will be particularly useful as online, self-service applications become more mobile and highly focused on particular information needs of individual end users. The number of such “public” applications is already humungous, but they are just starting to make their way into enterprise controlled “app stores.” This is where TCU will become important as such “mobile apps” will require constant updating to meet enterprise BYOD needs, as well as operational business demands.
Another perspective on application TCU will be its UC enablement in terms of immediate access to live assistance, e.g., “click-to-call/chat.” This factor will be a major source of additive labor costs, as well as a measure of end user satisfaction (internal staff, external customers). Mobile apps will become a major activity gateway to the UC Contact Center of the future, as increased access to information will precede the need to access assistance. So, the cost of application usage should include costs of optional related assistance.
Total Cost of Application and User Support
Although there may appear to be overlap with the above described usage costs, I am suggesting that support costs here will fall into the more traditional roles of IT for application software maintenance, associated hardware and infrastructure maintenance, new integrations, end user training, and “Help Desk” functions. Again, by applying analytics to application support activities, the value of individual application usage can be matched to support costs.
With the advent of managed, hosted cloud-based services, applications will be increasingly provided to end users through a variety of endpoint devices, many of which will be covered by mobile BYOD policies as far as costs and support are concerned. Further, hosted business services will be provided selectively on a subscription basis, which will facilitate usage management at the application level. However, the value and effectiveness of application use will still have to be carefully evaluated individually by business management.
The new world of UC enabled applications is going to be very flexible, but complex, and will require organizational management especially at the CIO level, to change their perspectives on planning, implementing, and evaluating the use the new technologies.
This post sponsored by the CIO Collaboration Network and Avaya
.
Sunday, March 18, 2012
All Applications Can be "UC Enabled!"
March 18, 2012
UC Is Not An Application!
By Art Rosenberg, The Unified-View
Everywhere you read, you see the label "Unified Communications" (UC) associated with person-to-person telephony, all forms of text messaging, and lately, video conferencing. UC itself is not a product or a service. It is an interoperable capability for improving the efficiency and flexibility of making contact and communicating with people by integrating the various communication and business process "applications" that people use. It doesn't matter what endpoint device is used, desktop, portable laptops, tablets, or smartphones, the applications that can enable people to flexibly communicate in their modality of choice, will be part of "UC."
I see a simple solution to that source of confusion. Rather than use "UC" as a vague noun, we will be better off using it as a standard adjective, i.e., "UC-enabled," for any communication application that is used for person-to-person contacts, as well as any automated business process application that initiates contacts with a human recipient. It is analogous to the term "open" used for standardized software, that can inter-operate/integrate with other system elements.
Different communication products and services can now be described as being 'UC-enabled" to show that they inter-operate with other communication applications at the user's choice of interface (voice, screen). Alternatively, I have simply put the "Unified" label into the name of the basic service or product, e.g., the "UC Contact Center," and "Unified Conferencing." By doing so, I differentiate it from legacy telephony call centers and indicate that different forms of contact and different user interfaces can be accommodated for different groups of end users and business applications.
Telephony, messaging (email, voice mail), chat, automated business applications, conferencing, social networking, can all be labeled as "UC-enabled" when they can seamlessly inter-operate from any user endpoint device in any modality. So, for example, email will be UC-enabled if it can be delivered by text-to-speech, voicemail retrieved as email, and all messaging applications (including IM chat) if they can be escalated to a real-time voice or video connection. Even that old buzzword, "Collaboration" can better be described as "UC-enabled" when it can contextually exploit various forms of communication within the context of the information being shared, not the other way around.
So, let's all start using "UC" as an adjective/modifier rather than as a vague noun for a communication product or service. This should not conflict with the basic business objective for being UC-enabled, i.e., "Communications integrated to optimize business processes." However, each specific communications application will have to be identified and authenticated as being "UC-enabled," and the different user interface options for each business application as well.
Thursday, March 15, 2012
Avaya and RADVISION UC Enable Video Conferencing
Copyright © 2012 The Unified-View, All Rights Reserved Worldwide
March 15, 2012
UC Enabled Video Conferencing Won't Require “Two-to-Tango”
By Art Rosenberg, The Unified-View/ UC Strategies Expert
The big news today was Avaya’s public announcement that it acquired RADVISION, Ltd., a leading provider of video conferencing and telepresence technologies over IP and wireless networks. While we have also seen video conferencing as a growing form of business communication, it has been always viewed as an expensive technology silo. By UC enabling video conferencing, it can now become a more flexible option for individual end users.
Avaya’s announcement today highlighted such UC flexibility in the form of “mixed-mode” conferencing, where individual participants have a choice of dynamic options including:
· “On camera” connection (conversational voice and video)
· Video viewing and voice connection
· Voice-only connection
· Sidebar communications (text messaging)
Such flexibility will be particularly useful for individual mobile users with smartphones and tablets, who may have to participate in a restricted mode because of their environment. This also means that people who want to communicate don’t all have to have identical endpoint devices or communicate in identical modalities.
According to Avaya’s announcement, “RADVISION's SCOPIA Video product line and expertise integrated with the open architecture of Avaya Aura® will bridge existing H.323 communications networks and SIP-based environments, delivering scalability and a user experience designed to be intuitive and easy to operate.”
In addition to supporting mobile devices for UC enabled conferencing, Avaya indicated that the technology was “cloud” ready, i.e., that the technology can be available as a service without investment in premise-based equipment. This combination, coupled with standards-based applications, open infrastructure and endpoints for ad-hoc and scheduled videoconferencing with room-based systems, desktop, and mobile consumer devices, will facilitate the establishment of practical organizational BYOD policy for mobile employees.
During today’s announcement call, I questioned Avaya about the target markets for their UC enabled video conferencing, and these were high on their list:
· Health care and medical devices
· Education markets for distance learning
· Contact center applications
· Financial services
· SMB ad hoc video conferencing
The multimodal, UC battle is on and Avaya is stepping up to the plate.
UC Summit For UC Channels and Consultants
Reseller channels can learn more about where multimodal business communications are going within the expanded context of UC by joining unified communications industry leaders at UC Summit 2012, the only channel and consultant-focused event for the Unified Communications industry.
This unique, invitation-only UC Summit in May, hosted by UC Strategies, is the place for experienced communication technology channels to get objective, expert advice on new business opportunities. This includes learning where UC-enabled applications are going, what leading vendors and service providers are offering in the way of software applications and tools, and opportunities for partnering with other, complementary specialist channels to satisfy the complex UC needs of a user organization.
Invitations are limited, so apply now to qualify for acceptance.


