Ingo Schnfeld, ATLAS, API, Emnekart 2006 Overview 1.ATLAS ELEKTRONIK and Knowledge Management 2.A Misunderstanding: ECM and Knowledge Management 3.Integrating Knowledge: Using Topic Maps by Means of EII 4.Pure Synergy: The ATLAS Development Process 5.Benefits & Conclusion Managing Knowledge in the Development Process Knowledge Management at ATLAS ELEKTRONIK Ingo Schnfeld Ingo Schnfeld, ATLAS, API, Emnekart 2006 ATLAS ELEKTRONIK: Knowledge Management nKnowledge Management is the business case nIntegrated holistic approach set up in 2000 nKnowledge Manager of the Year award in 2003 nFacets of ATLAS Knowledge Management Company culture Knowledge process Contents Knowledge assets Tools and technology nFacet Tools and Technology Currently running Hyperwave IS/6 as our knowledge repository Central web-based Enterprise Content Management System (ECM) Using the well known folder metaphor to categorize documents CultureProcess ContentsTools Ingo Schnfeld, ATLAS, API, Emnekart 2006 ATLAS ELEKTRONIK: ECM and Knowledge Management (1) ECM-KM solutionWhat ATLAS-KM really needs Almost managing only the covers or containers: documents Attach meta data to documents Other typical ECM features Handling the content of documents Handling arbitrary subjects Attaching meta data to subjects Creating relationships Powerful structuring mechanisms nSignificant shortcoming in most document-oriented systems: missing flexible tools to structure information and model meaning nDocuments are important, but in this sense they are nice to have! nCategorizing documents in folders doesnt correspond to the way people think Ingo Schnfeld, ATLAS, API, Emnekart 2006 A Misunderstanding: ECM and Knowledge Management (2) nWhat does it mean? How do people think? We use terminology to facilitate talking about matters We are able to describe the characteristics of things or matters We can explain how things relate to each other Thats exactly what Topic Maps do! nWe dont think in documents! But theyre useful for sharing knowledge. Categorizing documents in folders doesnt correspond to the way people think. Panoramic DetectorMeyersieck is inventor of inventor invention patentemployee Filing date:31 Aug 1985 App Number:DE Ingo Schnfeld, ATLAS, API, Emnekart 2006 A Misunderstanding: ECM and Knowledge Management (3) Peoples mental model Unified knowledge model Is controlled by is managed by requires signature of participates in must be used in combination with can not be used with must be proceeded by Source: Ontopia A/S Ingo Schnfeld, ATLAS, API, Emnekart 2006 Integrating Knowledge: Using Topic Maps by means of EII+ nEnterprise Information Integration (EII) Connects information instead of applications (EAI) Harvests other (unstructured) information resources Topic Maps: Building an integrated knowledge layer on top of the IT infrastructure Distributed information resources can be linked to the topics in the topic map nEII+ Connects information systems, and Peoples implicit knowledge nHow to apply EII+ pragmatically? Microarticles and predefined annotation types Topic TypesAssociation TypesScope Experience Best practice Lesson learned Ask the expert Open discussion Attach document [] depends-on relates-to best-used-with requires part-of [] Engineering Sales Procurement Quality Management Human Resources [] Ingo Schnfeld, ATLAS, API, Emnekart 2006 The ATLAS Development Process General Principle DB IS/6 Filer Harvester process OKS-driven Web server and OKS Web application HTTP HR HP General purpose Special purpose Merging! Ingo Schnfeld, ATLAS, API, Emnekart 2006 Before mergingAfter merging Merging Topic Maps Additional contact information about an employee after merging the general purpose HR topic map. The ATLAS Development Process Simple merging example Ingo Schnfeld, ATLAS, API, Emnekart 2006 The ATLAS Development Process Integrating stand-alone Topic Maps Modelled in ARIS Bid Manage- ment System Definition Develop- ment HW / SW System Integration Remaining Tasks (internal) Engineering Steering Configuration Management Ingo Schnfeld, ATLAS, API, Emnekart 2006 The ATLAS Development Process The overall connector: the process itself Bid Management System Definition Develop. HW/SW System Integration Remaining Tasks Engineering Steering Configuration Management Modular Components Configuration Management Patents Standards CAD Ingo Schnfeld, ATLAS, API, Emnekart 2006 Ingo Schnfeld, ATLAS, API, Emnekart 2006 Ingo Schnfeld, ATLAS, API, Emnekart 2006 Ingo Schnfeld, ATLAS, API, Emnekart 2006 The ATLAS Development Process: Benefits from a KM point of view (1) Single point of access nBridging wide spread information islands nenriched by peoples knowledge and experiences nAll relevant information are available in one consistent user interface nAddressing users retrieval problems Lower costs nEII cheaper than EAI EAI is often not necessary nExisting systems dont need to be changed and work as usual nEasy to extend information layer nThe Topic Map knowledge layer itself is valuable knowledge asset Ingo Schnfeld, ATLAS, API, Emnekart 2006 The ATLAS Development Process: Benefits from a KM point of view (2) Other benefits nHigher quality of search results nQuerying: Infer knowledge not explicitly modelled nImproved transparency in company information and knowledge structures Other helpful side effects nTopic Maps/EII+ lowers resistance on the part of any third parties; new systems provide resistance on-going discussions about pros and cons nTopic Maps spark interest in itself when used for integration purposes Ingo Schnfeld, ATLAS, API, Emnekart 2006 Conclusion Making Knowledge Management a success Experiences nAn ECM is no bound to succeed, but useful nUse existing systems and connect their information using Topic Maps nMerging is a killer feature realising a kind of information plug-in concept Best Practices nUse established knowledge structures people are familiar with nCreate modular Topic Maps and merge them as needed nUse a bottom-up approach nModelling instead of programming nBut dont underestimate the effort of developing harvesters Ingo Schnfeld, ATLAS, API, Emnekart 2006 Thank you for your attention! Your questions, please? Contact: Ingo Schnfeld