Joe Burton, CTO, Session Notes:
- Why is an architectural approach towards collaboration important? That's a question Cisco wants to answer - point tools are not enough.
- Example1: collaboration-enabled CRM process. Note: Reminiscent of "Collaborative CRM" concept defined by Meta Group years ago which has morphed into "Social CRM".
- Example2: virtualizing key business functions - scaling expertise, customer intimacy via video (Telepresence) just-in-time customer representative or expert.
- Example3: Streamlining complex human processes - follow-me, single number reach... reduce cycle time, coordination, process latency
- Devices (desktop, mobile, in-room)
- Collaborative Applications (conferencing, enterprise social software, customer care, messaging, telepresence
- Client Services (client frameworks)
- Collaboration Services (presence/location, tagging, semantic processing, real-time messaging, content services, social graph, etc)
- Medianet Services (transcoding, auto-discovery, auto-configuration, etc)
- Network Services (transport, signaling, QoS)
- Service Advertisement Framework: discovery protocol - device can go to network and broadcast/request capabilities ...
- SIP Session Management
- Survivable Remote Site Telephony/Voicemail
- Medianet Auto-Configuration
- XMPP as presence hub with interfaces and connectors to other presence providers
- Pulse Collect: deep packet analysis (web, blogs, wikis, documents, recorded audio/video - future: SaaS Apps, Conference Calls)
- Pulse Connect: Open Social Web Services API (profile data, presence server, policy engine)
Has Cisco gone into any more detail regarding ECP / enterprise ingegration for provisioning and single sign-on?
Posted by: Jackson Wilson | November 13, 2009 at 10:54 AM
Thanks for Joe Burton, CTO, Session Notes.. Has Cisco gone into any single sign-on?
Posted by: computers | November 30, 2009 at 02:27 AM