23.12.2012 Views

Preface for the Third Edition - Read

Preface for the Third Edition - Read

Preface for the Third Edition - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Real-time<br />

News<br />

Feeds<br />

Corporate<br />

Document<br />

Management<br />

Browser<br />

InfoMagnet Server<br />

Web<br />

Servers<br />

FIGURE B-55. Simple architecture <strong>for</strong> KMS 511<br />

Lotus Notes<br />

Database<br />

7. Systems 315<br />

World<br />

Wide<br />

Web<br />

Market-driven architectures. A third group of authors applies a more pragmatic<br />

approach and empirically distills <strong>the</strong> most important components of an organizational<br />

knowledge management environment which is integrated with more traditional<br />

data and document management systems as well as communication systems<br />

512 . The authors mostly rely on <strong>the</strong> offers of (a number of) vendors of standard<br />

software tools, plat<strong>for</strong>ms and systems to support KM or analyze <strong>the</strong> individual KM<br />

environments of organizations that are regarded as KM pioneers and develop <strong>the</strong>ir<br />

own KMS solutions. These architectures are mostly layer models. The number,<br />

naming and inclusion criteria of <strong>the</strong> layers differ from author to author. Examples<br />

<strong>for</strong> layered KMS architectures are:<br />

OVUM, also a vendor of KMS tools, developed a simple architecture <strong>for</strong> KMS<br />

based on an empirical study on ICT demands and supplies <strong>for</strong> KM (Versteegen<br />

1999). The architecture supports <strong>the</strong> four KM core processes capture, classification,<br />

sharing and understanding of knowledge and consists of six layers: (1)<br />

in<strong>for</strong>mation and knowledge sources, e.g., texts, DBMS, email directories,<br />

WWW and <strong>the</strong> knowledge workers <strong>the</strong>mselves, (2) infrastructure, i.e. email, file<br />

server and Intranet-/Internet-services, (3) in<strong>for</strong>mation and process management<br />

that is located in a knowledge repository, (4) a shared taxonomy, a knowledge<br />

map, (5) knowledge management services <strong>for</strong> discovery and collaboration and<br />

(6) a user interface that consists of a knowledge portal.<br />

The architecture presented by Applehans et al. (1999) is quite similar to <strong>the</strong><br />

OVUM architecture and also comprises six layers (see Figure B-56): (1) in<strong>for</strong>mation<br />

and knowledge sources, called repositories, (2) transport layer, which<br />

corresponds to an Intranet infrastructure, extended by collaboration and stream-<br />

511. Source: CompassWare 1998.<br />

512. See e.g., Applehans et al. 1999, 87ff <strong>for</strong> a layered knowledge architecture, Bach 1999,<br />

69 who proposes a tool architecture <strong>for</strong> business knowledge management, CZ 1999, 13<br />

<strong>for</strong> <strong>the</strong> comprehensive KM architecture proposed by <strong>the</strong> Meta Group, Versteegen 1999,<br />

118 who describes OVUM’s six-layer KMS architecture, Seifried/Eppler 2000, 31ff<br />

who suggest a structured set of functionality expected from knowledge management<br />

suites and Vieser 2000 who presents <strong>the</strong> Siemens three-layered architecture <strong>for</strong> ICT<br />

tools, services and KM applications.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!