ccd 2013: einführung von confluence wiki als collaboration plattform

11/21/2013

Products Solutions Services

Confluence & JIRA Community Day 2013

Introducing Confluence as corporate collaboration platform

Slide 1 Stephan Hezel

11/21/2013

Table of contents

Confluence & JIRA Community Day 2013 - Endress+Hauser

• The Endress+Hauser Group• Start Situation• Approach• Outcome



11/21/2013

The Endress+Hauser Group

• Introducing “People for Process Automation”


11/21/2013

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

Our fields of activity



11/21/2013


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


11/21/2013

• Holding company in Reinach, Switzerland• 21 production facilities in 12 countries• Sales centers and representatives in more than 100 countries• Regional sales support centers


Our structure



11/21/2013

Start Situation


11/21/2013


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



11/21/2013

Approach


11/21/2013


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


11/21/2013


“Wiki” Rollout Project

• July 2011: Group project started• 40 Members out of different entities,

disciplines, countries• Prepare a roll out for the Endress+Hauser Group

& ensure sustainable operation

Structure & Rights

management

Lifetime Framewok

Integration

Communication & Education


11/21/2013


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


11/21/2013


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



11/21/2013

Outcome


11/21/2013


Current facts and figures

0

20'000

40'000

60'000

80'000

100'000

120'000

140'000

Okt09

Dez09

Feb10

Apr10

Jun10

Aug10

Okt10

Dez10

Feb11

Apr11

Jun11

Aug11

Okt11

Dez11

Feb12

Apr12

Jun12

Aug12

Okt12

Dez12

Feb13

Apr13

Jun13

Aug13

Clue Usage Statistic

Page views

Page growth

Page creation

Pilot Go Live

Rollout Phase


11/21/2013


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


11/21/2013


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


11/21/2013


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


11/21/2013


Thank you very much for your attention


ccd 2013: einführung von confluence wiki als collaboration plattform

Technology