Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CCD 2013: Einführung von Confluence Wiki als Collaboration Plattform

1,488 views

Published on

Veranstaltung "Confluence & JIRA Community Day 2013" in Frankfurt/M. am 21. November 2013.
Eine Präsentation zum Thema "Einführung von Confluence Wiki als Collaboration Plattform" von Stephan Hezel, Application Manager Endress+Hauser Consult AG

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

CCD 2013: Einführung von Confluence Wiki als Collaboration Plattform

  1. 1. Products Solutions Confluence & JIRA Community Day 2013 Introducing Confluence as corporate collaboration platform Slide 1 11/21/2013 Stephan Hezel Services
  2. 2. Confluence & JIRA Community Day 2013 - Endress+Hauser Table of contents • • • • The Endress+Hauser Group Start Situation Approach Outcome Slide 2 11/21/2013 Stephan Hezel
  3. 3. Products Solutions The Endress+Hauser Group • Introducing “People for Process Automation” Slide 3 11/21/2013 Stephan Hezel Services
  4. 4. Confluence & JIRA Community Day 2013 - Endress+Hauser Our fields of activity Wherever you are, whatever you do: you are surrounded by products manufactured by the process industries Thanks to process engineering, substances can be modified, merged or transformed, for example by: • mechanical processes • chemical and biochemical reactions • impact of heat Slide 4 11/21/2013 Stephan Hezel
  5. 5. Confluence & JIRA Community Day 2013 - Endress+Hauser Our offering We provide instruments and systems for tasks in the field of • Level measurement • Flow measurement • Pressure measurement • Temperature measurement • Analytics • Data acquisition • Sampling Slide 5 11/21/2013 Stephan Hezel
  6. 6. Confluence & JIRA Community Day 2013 - Endress+Hauser Our structure • • • • Holding company in Reinach, Switzerland 21 production facilities in 12 countries Sales centers and representatives in more than 100 countries Regional sales support centers Slide 6 11/21/2013 Stephan Hezel
  7. 7. Products Solutions Start Situation Slide 7 11/21/2013 Stephan Hezel Services
  8. 8. Confluence & JIRA Community Day 2013 - Endress+Hauser Starting situation – challenges • Decentralized organization • Forced for internal competition • Less communication, cooperation • Information, communication silos • No common platform (except intranet) • No central tool where everyone can contribute • No common file share vs. N- file shares • Team Rooms well-established • E-Mail in use for every kind of collaboration Slide 8 11/21/2013 Stephan Hezel
  9. 9. Products Solutions Approach Slide 9 11/21/2013 Stephan Hezel Services
  10. 10. Confluence & JIRA Community Day 2013 - Endress+Hauser Bottom-up approach • Bottom-up idea enables central wiki (confluence installation) • Pilot since 2009: 5000 pages available within some month • Representative user group with key user in some locations (mainly Marketing, R&D, IT)  Critical mass reached  Pages, number of user and support requests grew  No information structure, strategies, rules and responsibilities, perception within the entire Company Slide 10 11/21/2013 Stephan Hezel
  11. 11. Confluence & JIRA Community Day 2013 - Endress+Hauser “Wiki” Rollout Project • July 2011: Group project started • 40 Members out of different entities, disciplines, countries Integration • Prepare a roll out forLifetime the Endress+Hauser Group Framewok & ensure sustainable operation Communication & Education Slide 11 11/21/2013 Stephan Hezel Structure & Rights management
  12. 12. Confluence & JIRA Community Day 2013 - Endress+Hauser Project outcomes • Name change wiki Clue (Collaboration Blue, hint) • Redbook (SSO, Welcome Layer, Navigation) • Concept (Governance Book) for • Targets • Processes • Organizational concept (roles) • Lifecycles • Quality concept • Further development of the system • Core Group Slide 12 11/21/2013 Stephan Hezel
  13. 13. Confluence & JIRA Community Day 2013 - Endress+Hauser Rollout • Advertising in internal magazines, intranet • Selection and introduction of Local Responsible • Organized local rollouts (training, info-meetings, workshops) • Go Live July 2012 with “Big Bang”: • Adopted system • “Teaser Video” • Intranet page • Online tutorials • Magazines • Rollouts Slide 13 11/21/2013 Stephan Hezel
  14. 14. Products Solutions Outcome Slide 14 11/21/2013 Stephan Hezel Services
  15. 15. Confluence & JIRA Community Day 2013 - Endress+Hauser Current facts and figures Clue Usage Statistic 140'000 Rollout Phase 120'000 100'000 80'000 Page views Page growth 60'000 Page creation 40'000 20'000 0 Okt Dez Feb Apr Jun Aug Okt Dez Feb Apr Jun Aug Okt Dez Feb Apr Jun Aug Okt Dez Feb Apr Jun Aug 09 09 10 10 10 10 10 10 11 11 11 11 11 11 12 12 12 12 12 12 13 13 13 13 Pilot Slide 15 Go Live 11/21/2013 Stephan Hezel
  16. 16. Confluence & JIRA Community Day 2013 - Endress+Hauser Current use cases • Collaborative • Project documentation • Error recording / Experience collection • Continuous development of IT tools • Continuous development of processes (technical documentation, social media etc.) • Writing user manual • Preparing marketing material • Preparing Group Standards • Platform development • Organizing Events Slide 16 11/21/2013 Stephan Hezel
  17. 17. Confluence & JIRA Community Day 2013 - Endress+Hauser Learnings (I) • Rollout and Acceptance  • Rollout where needed  Focus on promotion • Clear responsibilities in entities  Self responsibility • Target orientated rollout = sustainable  use case absolute necessary • Implementation of Clue into daily work  move work to Clue • Involvement  • Involve early  Talk to people • Collect feedback, visualize and save  Documentation Slide 17 11/21/2013 Stephan Hezel
  18. 18. Confluence & JIRA Community Day 2013 - Endress+Hauser Learnings (II) • Need for  • Acceptance from management • Use cases have to be analyzed • Simple and general adoptable use cases • Implementation into processes  “Group Standards” • Organizations need time  • Time for Change management: Communicate clear and consistent, stick to the messages • Adoption: Every company is different • Keep listening and developing • Lifecycle  still an open topic Slide 18 11/21/2013 Stephan Hezel
  19. 19. Products Solutions Thank you very much for your attention Slide 20 11/21/2013 Stephan Hezel Services

×