KNOWLEDGE CREATION AND

KNOWLEDGE MANAGEMENT
ARCHITECTURE
Main Topics
 Knowledge Creation and Sharing
 Knowledge Infrastructure
 Knowledge Management
Architecture
 Build versus Buy Decision

2
KNOWLEDGE CREATION
 Dynamic activity that can
enhance organization
success and economic
well-being
 Driver of innovation
 Involves knowledge
acquisition, selection,
generation and sharing
 Maturation- translates
experience into knowledge
3
 Impediments to Knowledge
Sharing
Compensation Personality
Organizational
Recognition culture
Ability utilization
Vocational
Creativity reinforcers Knowledge
Good work environment sharing
Autonomy
Job security Attitude
Moral values Company
strategies and
Advancement policies
Variety Work Norms
Achievement
Independence
Social status
4
Nonaka’s Model of Knowledge
Creation and Transformation
TACIT TO TACIT
(SOCIALIZATION)
E.G., INDIVIDUAL AND/OR TEAM
MEETINGS
EXPLICIT TO TACIT
(INTERNALIZATION)
E.G., LEARN FROM A REPORT E.G., CREATE A WEBSITE FROM
AND DEDUCE NEW IDEAS
TACIT TO EXPLICIT
(EXTERNALIZATION)
E.G., DOCUMENT A
BRAINSTORMING SESSION
EXPLICIT TO EXPLICIT
(COMBINATION)
SOME FORM OF EXPLICIT
KNOWLEDGE
5
 KNOWLEDGE
INFRASTRUCTURE
 People core: Evaluate employee profiles
 Content core: Identify knowledge centers
 Technical core: The total technology
required to operate the knowledge
environment
People Content

Technolog
y 6
Identifying Knowledge Centers

Job openings, Competition data,

Benefits Sales volume,
Leader sales
information
Human
Resources
Sales

Customer
Strategies Service
Tools Marketing
R&D
Complaint rate,
Advertising
Satisfaction
information

7
 Stages of KMSLC
Evaluate Existing
Infrastructure √
Form the KM Team √
Knowledge Capture
√
Iterative Rapid Prototyping
Design KM Blueprint ←
Verify and validate the KM
System

Implement the KM System

Manage Change and

Rewards Structure

Post-system evaluation
8
 .....

Layers of KM Architecture
1 User Interface
(Web browser software installed on each user’s PC)

Authorized access control

2 (e.g., security, passwords, firewalls, authentication)

Collaborative intelligence and filtering

3 (intelligent agents, network mining, customization, personalization)

Knowledge-enabling applications
4 (customized applications, skills directories, videoconferencing, decision support systems,
group decision support systems tools)

Transport
5 (e-mail, Internet/Web site, TCP/IP protocol to manage traffic flow)

Middleware
6 (specialized software for network management, security, etc.)

The Physical Layer

(repositories, cables)
7

Databases Legacy applications Groupware Data warehousing

(e.g., payroll) (document exchange, (data cleansing,
collaboration) data mining) 9
The User Interface (Layer 1)
 User interface
design focuses
on consistency,
relevancy, visual
clarity,
navigation, and
usability

10
Authorized Access Control
(Layer 2)
Extranet
Internet Intranet
Public Clients
Company •Suppliers
•Vendors
•Partners
•Customers
•Human resource
•News/events
information
•Marketing
• Product information
•Production
•E-commerce •Sales information
information
•Careers •Sales •Collaboration/cooper
information ation

•Strategic plans
11
Collaborative Intelligence and
Filtering (Layer 3)
 Personalized views
based on stored
knowledge
 Groupware to facilitate
both sync- and
asynchronous
interaction and
discussion
 Intelligent agents
reduce search time for
needed information
12
 Knowledge-Enabling
Application (Layer 4)
 Referred to as value-added
layer
 Creates a competitive edge
for the learning organization
 Provides knowledge bases,
discussion databases,
automation tools, etc.
 Ultimate goal: show how
knowledge sharing could
improve the employees 13
 Transport Layer (Layer 5)
 Most technical layer to
implement
 Includes LANs, WANs,
intranets, extranets, and the
Internet
 Ensures that the company
will become a network of
relationships
 Considers multimedia, URLs,
graphics, connectivity speeds,
and bandwidths 14
Middleware (Layer 6)
 Focus on interfacing with
legacy systems and
programs residing on
other platforms
 Designer should address
databases and applications
with which KM system
interfaces
 Makes it possible to connect
between old and new data
formats
15
Physical Repositories (Layer 7)
 Bottom layer in the KM
architecture
 Represents the physical
layer where repositories
are installed
 Includes intelligent data
warehouses, legacy
applications, operational
databases, and special
applications for security
and traffic management
16
 Build In-House, Buy, or
Outsource?
 Trend is toward ready-to-use,
generalized software packages
 Outsourcing is also a trend,
releasing technological design
to outsiders
 Question of who owns the KM
system should be seriously
considered

17
Build vs. Buying
Option Cost Time Factor Customization
In-house Usually high Much lower than High, depending
development development by on quality of
user staff

Development Usually low Depends on skills High to the user

by end users set, system priority, specifications
and so forth

Outsourcing Medium to high Shorter than High

in-house

Off-the-shelf Low to medium Nil Usually up to

Solution 80% usable
18
End of Lecture Three

19
 In Class Discussion Exercise
 Assume you are the person
responsible for making
decision on a KM project
 How would you decide to
build or buy?
 Based on the key elements
compared, and
 The current state of your
organization preparedness
(thinking in terms of maturity
in layers of KM architecture)
20
Knowledge Sharing Via
Teamwork
Initial
knowledge

Outcome
is realized

Team performs
a job Outcome
compared
to action
New knowledge
reusable by same
team on next job
New
Knowledge experience/
captured and knowledge
codified in a gained
form usable by
others
21