Enthinnai a social enterprise app


Published on

EnThinnai is a social enterprise app that has all the service objectives of a social network, but the scope of federation is upto the sharing enterprise; it can share with non-users as well while ensuring the id of the viewer.

Published in: Social Media
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Enthinnai a social enterprise app

  1. 1. EnThinnai: A Social Enterprise App Aswath Rao http://www.enthinnai.com
  2. 2. Summary  Requirements  Description of EnThinnai  Cloud-ready Architecture  Roadmap
  3. 3. Enterprise-specific Requirements      Provide collaborative tools New Gen workforce is used to and is expecting But ability to maintain privacy and confidentiality requirements of a corporate entity Federated identity scheme All content must be corporate knowledge-base Presence information    Real-time Communication tool    Availability of a specific individual Availability of an individual with some functional responsibility/expertise Text, Voice and Video Both internal and external Collaboration tools  Conferencing, Screen sharing, collaborative editing
  4. 4. EnThinnai Overview  A repository of digital information of a user and shared with one or more "buddies"  Users and Buddies are identified by their OpenIDs       Buddies don't have to be EnThinnai users A buddy can be assigned a "null" OpenID An Enterprise can have top level control on which OpenIDs can be included EnThinnai is a Unified Communications (UC) Platform      Or by Enterprise issued responsibility tags Or by self expressed interest and experience (much like lists) Pull contact-specific Presence information IM Voice/Video Archiving of chat sessions Access to any stored information can be embedded in any web page
  5. 5. Features and Capabilities  Availability Status ("Presence")    Notes      Cross between email and blog It is structured like email It is stored and accessed like a blog post File sharing Contact Information     Customizable for a single or a group of buddies Buddies pull this information when required Address Phone information Internet methods: email, IM IM/Voice/Video   Utilizes WebRTC/Websocket Every chat session is recorded and archived
  6. 6. Use Case: Collaboration  Use Notes to record an ongoing exchange of ideas and viewpoints  Easily add new members to the team at a later date  Use file sharing to share documents  Use IM/Voice/Video to have dialog  IM sessions are archived for later reference  Easy to add partners and customers because of use of OpenID  Just as easily the access permission can be removed
  7. 7. Use Case: Customer Interaction Access URLs can be placed in different places in the Company's web site  Customers can easily reach appropriate people associated with the customer's need       Product description page -> Sales organization FAQ page -> Support Career section -> HR Deep context -> Fine routing based on Cookies and other info  Much like Amazon’s Mayday button Archived conversations   Continue an interactive session at a later date Efficient way to build a Knowledge Base
  8. 8. Cloud-ready Architecture  Service definition ensures the growth is linear and not polynomial     EnThinnai is both low-end and high-end scalable    Presence information is pulled when needed Shared content is pulled when needed When a new user joins the system, only the server associated with that user is impacted 5-user (unlimited buddies) system can run on a single Raspberry Pi It can run on a Public cloud like Amazon Web Services Designed for cloud    Service logic runs on an instance (can be added incrementally as new users are added) Bulk data/files are stored in storage instances (can be added incrementally as new data are stored) Cloud provided backup for failovers
  9. 9. Chat Application  User generates a “contact link” and shares with others  As a link in a web page, email signature or biz card  By embedding an iFrame  Can be “deep contexted” – so user will know the context of a call from a buddy  Email soliciting comments on a doc will contain a link identifying that doc  When a call is received, the UI at the callee end will identify the doc and the user can view the doc easily
  10. 10. Generating Contact Link
  11. 11. Look of an iFrame
  12. 12. Initial screen
  13. 13. After sending the first message & Permission setting Caller’s view Callee’s view
  14. 14. Full Chat Session (in progress) • Simultaneous IM and Video • Can end just video • Mute one or more video components • Ability to Buzz the other end to get attention
  15. 15. Product Roadmap  Multi-party chat  Real-time document editing  Second Life kind of room sharing  Permission based on Enterprise issued  responsibility tags  Permission based on self expressed interest  and experience  Encryption of data   During data transfer Storage
  16. 16. Background
  17. 17. Background  Gen Y and Millennials are dominating the  workforce  They require social collaborative tools  They have used tools like Facebook and  Twitter  They intuitively know the benefits  But Enterprises have fiducial and  regulatory constraints
  18. 18. Features of Social Networks  Easy information sharing  Condensed information with links for details  Quick dissemination  Spread by others using codified “forward” mechanism  Percolation of good ideas  Ability to “vote” up or down  Real-time 1-1 and group communication  Modeled after Facebook and Twitter  But blind emulation of these networks may not  be appropriate
  19. 19. Benefits  Customer focus  Increased engagement  Faster response  Quick lead conversion  Workplace focus  Instant collaboration among employees  Weak-ties become collaborators  Weakened departmental silos
  20. 20. Corporate Realities  But corporations have regulatory requirements and fiducial  responsibility for data control and access control   Business partnerships and customer interactions require ease  of federation at both the enterprise and individual levels       Both inclusion and exclusion must be easily accomplished Real-time Communication needs must be addressed   Need to allow for limited sharing Multi-modal Permission based Flow model is not always appropriate Ability to add new people to previously shared content Repository of corporate knowledgebase These suggest some desired attributes of Enterprise Social  Software
  21. 21. Identity and Authentication  Simple federation implies that identity  must be user-centric  Organization control requires filtering  capability  Must allow for different grades of  authentication  Strong for sharing confidential data  Non-existent for casual and first-time visitors
  22. 22. Information Exchange and Sharing  email is a widely used tool  Though  It widely despised is a repository of organizational memory  But difficult to pass it onto new employees  The trail may be diffused  Blogs  But and wikis are better models they lack access control
  23. 23. Presence Information  Simple online/offline is meaningless in an always on world  Rich Presence will have multiple sources  Presence information will depend on the receiver  Security considerations while federating Presence information
  24. 24. Real-Time Communication  Need for multi-modal communication  Require a way to escalate the mode of communication using a permission model    Text-based communication is less intrusive Voice communication is richer Video has its own advantages, but most intrusive  Persistent sessions  Organizations may require the ability to archive communication sessions
  25. 25. Collaboration Tools  Real-time, collaborative editing of documents  Multi-party conferencing  Screen sharing  Second Life like virtual world based collaboration session  Again ability to keep the session persistent and ability to archive