Unified communications is a buzzword that's front-and-center for many organizations this year. Some are already deploying various UC technologies (UC is one of the top three "recession-proof" technologies in Nemertes' 2009 benchmark). And many are building out long-term UC strategies.
But what does migrating to UC really mean? Even the simplest initiatives — such as rolling out unified messaging (UM) or deploying desktop video — can create major upheavals in business processes and operations. In many respects that's a good thing: sales teams close business faster, for instance, and geographically-dispersed teams can collaborate more effectively. But IT folks shouldn't underestimate the monkey-wrench that UC throws into long-established routines and processes.
For starters, there's that whole "unified" moniker. Like "convergence" before it, "unified" communications requires some the coming together of IT groups that were historically separate. Just as convergence (a.k.a. VoIP) was the catalyst that ultimately joined networking and telecom teams, UC will ultimately integrate multiple IT silos, particularly networking, desktop support and messaging.
To Continue Reading: Click Here
---------------------------------------------------
Source: networkworld.com
By: Johna Till Johnson
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment