- Capgemini leverages social networks and wikinomics to enable knowledge sharing across its 91,000 person global organization. - The company implemented an internal knowledge management platform using open source tools like Drupal, phpBB, and MediaWiki to provide search, communities, profiles, tagging and other collaboration features. - The architecture was designed for scalability, security integration, and to be stateless to enable hosting in the cloud and reduce long term costs of ownership.

1. Réseaux sociaux et wikinomics au cœur de Capgemini, l'exemple du Denis Lafont, Directeur Technique Capgemini

2. How to leverage knowledge in a 91.000 people (distributed) organization ?

3. How to leverage knowledge in ?

4. What is Knowledge Management?

9. KEY PRINCIPLES

10. No more KM organization - Everyone is in control anyone can create communities, tags, publish, vote,… No more knowledge manager "doing it for you" No more pre-defined heavy processes No authorization or validation required No more user manual From Co LL ection to Co NN ection

11. express your opinion ask the expert let people know you exist share your knowledge find who/what you need help promoting valuable content join a community so… what will be different with sharing to connect … stay in touch … and be ready for that next deadline collaborate with your peers connect now… connecting to share

12. First prototype delivered in Sept. 2007 Official launch 01/2009

13. Core KM Infrastructure Capgemini’s SSO Search References & Credentials On demand Community Spaces Personnal Spaces Capgemini SSO Search Knowledge Exchange (Forums) Collaborative Writing (Wiki) Search Profile Manager People Finder Meta datas Management Free tagging Voting

14. Detailed functional coverage User Interface & Easy of user WYSIWYG Editor Capgemini’s Look & feel Drag ‘n drop not yet available, will be in future release of Drupal Human friendly naming scheme Mail, RSS Automatic glossary Automatic alink Web 2.0 features Live Search Free tagging on content Community & Authors Tag Cloud Management Community oriented features (Organic Groups) Each user can create its own communities Each community can have its own private content A community can inherit content from another one My Network User Contribution Measurements Advanced voting system Content Recommendation Personnal Spaces Advanced Profile Manager, fully configurable Update from the Capgemini’s Directory Peer finders Forums Fully integrated with e-mail Web Semantics URI Standardization Semantic: Compliant with Microformats /vocabularies Shared taxonomy Search Integration with Google Search Security model integration Security SSO integration Role based access, can be imported from Capgemini LDAP Capgemini group’s tools integration Integration with Subversion Mailing list integration Easy creation of new type of content Bids, Methods, Software Components,….. Statistics Trends Loyalty Specifics to Capgemini Strongly integrated with the solution (ex: role based statistics) Performance Throttle management Aggressive/Normal caching strategy Valeo Service e-Portal Capgemini Proposal- Version 1.0 2006/09/11 – page ©2006 Capgemini ADC - All right reserved

15. KEY ARCHITECTURE DRIVERS

16. Key Architecture Drivers 3 Months delivery for beta 1 Tight Budget Existing wiki.capgemini.com reuse Constraints Foster Innovation and “human network effect” -> Let users build the system on demand -> Any object is typed, without strong constraints Low TCO Anticipate future needs Semantics, work lifestream, automatic tagging, micro blogging… Linear Scalability Add as many front/back end as we need, without redesign/extra costs -> Stateless architecture Ready for the Cloud ->Multiple Caching strategies Reduce TCO in Run mode - >As much off the shelves features as possible IT Drivers Business Drivers

17. SOLUTION ARCHITECTURE

18. Selected solution Content management system: Drupal Forum platform: phpBB Wiki environment: MediaWiki Google Search Google Analytics

19. Old school forums system Was the only one to offer round tripping feature A better choice now would be Drupal forums + microblogging « à la » twitter Excellent performance when no document security managed Very restricitive security management (late binding only) Still poor features comparing to modern search engines (FAST, Vivisimo, Exalead,…) Great Mindshare, low features Legacy choice Go Confluence, Mindtouch (or Drupal, MOSS 2007, Ensemble,…) Incomparable features /costs !!

20. Lessons learnt Web 2.0 features and impact on architecture Free tagging is not that a nightmare (today: 80.000 tags for 20.000 users) Social networking everything is costly Google is your friend. Like Yahoo  Follow Yahoo front end best practices Front end is really 40 of perceived performance by users Think Stateless Linear scalability at day 0 make you sleep at night Ready for Amazon EC2, Flexiscale, Sclar… Build the trust with your users. Bullet proof your Home page & search engine Do not choose an open source solution, choose a community KISS Freetagging without fancy stuff Search, REST style Security when you REALLY need it