![](bg2.png)
“Hyper Text type” organization, which refers to
“Hyper Text” originally developed in the computer
science field (Nonaka and Takeuchi, 1995).
Figure 1: The hypertext organization (Nonaka and
Takeuchi, 1995).
Figure 1 shows the “Hyper Text type”
organization. The layer in the center of the figure is
a business system layer in which normal routine
work is done. As the bureaucratic structure is
suitable for its efficiency, this layer is a hierarchical
structure. The top of this structure is a project team
layer, in which many project teams are engaged in
product development and the like. Members of these
teams are gathered from many divisions of the
business system layer, and engage in one project
until it is finished. When the team finishes the task,
it returns to the knowledge base layer, draws up a
knowledge inventory describing successes and
failures of the project, and returns to the business
layer. Based on his work experience at an enterprise
where he worked, the writer thinks that even if the
aforementioned knowledge is prepared, if the
situation does not enable its reuse, in cases where
part of the description needs revision or where
another project team wants to refer to it, accessing
the inventory is very difficult. Mainly using cases of
European enterprises, Enkel and others proposed a
knowledge network for the growth of enterprises
consisting of three layers (Enkel, 2007). Those cases
present a facilitating condition summarizing a
management methodology practiced by enterprise
management, a knowledge process regarding
knowledge work by interaction among employees,
and a reward structure and meeting methods and
communication methods serving as tools to support
the knowledge process. The framework designed by
Enkel and others is a model to relate and
comprehensively manage the business strategy with
systems and tools that support the business process.
However, this framework is different from an
enterprise organizational structure which is the target
of the system proposed in this paper. In addition to
this, Duncan (Duncan, 1979) and Ackoff (Ackoff,
1989) advocate building relationships among data
for intra-enterprise knowledge distribution, but both
of these differ form the proposal of this paper in the
intended organizational structure and the data link
structure.
2.2 Knowledge Management System
In recent years, computerized documents and email
have been used for in-house communication. In
enterprises, in-house knowledge distribution based
on a community called a “Community of Practice”
(CoP) or “Community of Interest” (CoI) proposed
by Wenger and others has been introduced into
business management (Wenger, 2002). Here, CoP
signifies a community where knowledge effective
for business performance is exchanged, and CoI
signifies an informal community where knowledge
of wide interest to employees is distributed. Based
on this principle, Lavoué proposed a model that
connects produced knowledge to activities proposed
by the CoP (Lavoué, 2009). On the other hand,
Benjamins and others used techniques of ontology
engineering in their approach to knowledge
management systems (Benjamins, et al, 1998). The
approach allows the discovery of knowledge that is
not explicitly known but can be deduced based on
general knowledge which is captured in the
ontology). Figure 2 shows overview of the approach.
Figure 2: An Ontology-based approach (Benjamins, 1998).
An ontology of the subject matter must build,
which is used to characterize the subject matter, for
instance to fill the ontology with instances. A
intelligent web crawler receives a query in term of
the ontology, consults them using the ontology and
generates an answer. Though the techniques of
ontology engineering are applied to the proposed
document management system described later in this
THE RESEARCH OF KNOWLEDGE MANAGEMENT SYSTEM FOR SUPPORTING HYPER TEXT TYPE OF
ENTERPRISE ORGANIZATION
313