There’s been a lot of discussion about the definition of UC and what it means, and if UC is the right term to use or not. Is there consensus on what are the categories that go into making a UC solution? Also, what makes something a UC product or solution? For example, is voicemail a UC solution?
Jim - in the "big picture", I really don't think it matters exactly how we define UC or what goes into it. Voice Mail? IP/PBX? Collaboration? Who cares (except for the vendors who want to be offering "UC products/solutions"). Does the end-user care if they're investing in a UC solution or do they care if they're investing in a solution that has a positive impact on their business in some way? What good does it do if we end up paralyzing resellers and buyers as they try to figure out if it's UC or not UC? If the solution, whatever it is, improves a process in my business through better communication of one sort or another - I'm interested!
Some resellers talk about having a "UC story" to tell their customers. It's NOT about UC! It's about improving productivity so a company can do more with fewer people in today's economy. It's about reducing expenses, increasing profitability, providing better service to customers, meeting the needs of a mobile workforce, and much more. But it's NOT about UC.
So how do we define UC and what is and isn't a part of UC? UCStrategies has the definition that describes UC in terms of what it does. That's more than enough!