10
Nov

Cisco Collaboration Summit: The Right Foundation For Collaboration

Posted by admin | No Comments

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 Reference Architecture for collaboration (logical diagram illustation) 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) Simple use case scenarios discussed that exercise architectural components (e.g., reduce travel expenses) Real-time voice and video 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 Context: Presence XMPP as presence hub with interfaces and connectors to other presence providers Context: Network-based Tagging 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) Intercompany Media Engine Intercompany Cisco TelePresence Client Services Framework: multi-platform multi-media softphone without a user interface ... can plug-in behind Microsoft Office Communicator, Sametime, etc ECP platform diagram: MVC framework,  BOSH, SIP/SIMPLE, IMAP. SOAP, REST, JCR, CMIS, open social, CMIS, RDF/SPARQL, portlet standards, Missing on slide: ATOM, RSS but believe it's in there - wonder about Open Search, FOAF and XFN

Link:
Cisco Collaboration Summit: The Right Foundation For Collaboration

Bookmark this post:
Digg Del.icio.us Reddit Furl Google Bookmarks StumbleUpon Windows Live Technorati Yahoo MyWeb

Comments are closed.