Difference between revisions of "Explicit knowledge"

From NKM WIKIDOC
Jump to: navigation, search
(→‎Related articles)
(→‎Definition)
 
(41 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 +
<!--
 
{{Monica}}
 
{{Monica}}
−
{{Andrey}}
 
−
{{Anatoly}}
 
−
{{Csaba}}
 
  
−
{{Clustering stage}}, {{Tidy1}}
+
{{DavidBeraha}}
  
−
{{Foundation}},  
+
{{Complete}},
  
−
{{Content}}
+
{{Consolidation stage}},
  
 +
{{Priority}},
 +
 +
{{Foundation}}
 +
-->
  
 
==Definition==
 
==Definition==
−
{{PAGENAME}} is knowledge {{ {{PAGENAME}} 4}}
+
{{ {{PAGENAME}}}}
  
 
== Summary==
 
== Summary==
−
One paragraph summary which summarises the main ideas of the article.
+
Explicit knowledge can be documented in useful forms such as operating manuals, files, reports, drawings, etc.
 +
Explicit knowledge can also be non-codified, but articulated and codifiable. There is much discussion about the distinction between [[Information|information]] and explicit knowledge, but for practical purposes, here they will be used interchangeably.
  
 
== Description==
 
== Description==
−
{{PAGENAME}} is knowledge {{ {{PAGENAME}} 4}} This knowledge can be readily transferred to others.
+
Explicit knowledge can be readily [[Sharing | transferred]] to others.
  
−
===Forms of explicit knowledge===
+
The most common forms of codified explicit knowledge are documents, drawings, calculations, icons, designs, multimedia, [[Database|databases]], [[Taxonomy|taxonomies]], [[Knowledge map|knowledge maps]] documented procedures and manuals.  
−
The most common forms of codified explicit knowledge are documents, drawings, calculations, icons, designs, multimedia, databases, [[knowledge representation]] (i.e. taxonomies, knowledge maps) documented procedures and manuals.
+
  
−
Non-codified explicit knowledge (i.e., knowledge that is conscious to the knowledge bearer) is for example existing non-documented procedures in an organization
+
Non-codified explicit knowledge (i.e., knowledge that is conscious to the knowledge bearer) includes for example existing non-documented procedures in an organization.
  
−
== ==
+
There is much discussion about the distinction between [[Information|information]] and explicit knowledge, but for practical purposes of managing these two (similarity of tools and methods), they will be used interchangeably here.
  
 +
The object can be information or explicit knowledge, depending on the recipient. The next section illustrates this thin boundary.
  
−
== Description==
+
===Illustrative examples===
−
Explicit knowledge is that which can be contained and conveyed in [[Document|documents]], drawings, calculations, designs, databases, procedures and manuals. This type of [[Knowledge|knowledge]] is also referred to as [[Information|information]]. Explicit knowledge can be recalled and articulated by the bearer, and subsequently recorded (for example, RWM documentation and [[Database|databases]]).
+
* Expert (rule-based) systems contain information that allow an independent person to act upon it - hence it is considered explicit knowledge
−
 
+
* Without an expert, NPP documentation will not allow an independent person to build and run an NPP - hence it is [[Information|information]]  
−
'''Source:''' [[Knowledge management for radioactive waste management organisations ]]
+
* Power failure in an NPP is information for the general public (meaning: not able to operate), but knowledge for the operators (meaning:danger)
−
 
+
−
== Description==
+
−
Explicit knowledge is contained and conveyed in documents, drawings, calculations, designs, databases, procedures and manuals. Explicit knowledge is knowledge that has already been codified (i.e. written down) or declared.
+
−
 
+
−
'''Source:''' [[Comparative Analysis of Methods and Tools for Nuclear Knowledge Preservation]]
+
−
 
+
−
==Description==
+
−
Explicit knowledge is considered to be all the [[Knowledge|knowledge]] that can be easily articulated and expressed in writing. This mode of knowledge is contained in [[Document|documents]], drawings, calculations, databases, procedures and manual. The quality assurance system (QAS) should provide for the management of this kind of knowledge.
+
−
 
+
−
'''Source:''' [[National approaches and strategies for Nuclear Knowledge Management]]
+
−
 
+
−
==Description==
+
−
Explicit knowledge is contained in documents, drawings, calculations, designs, databases, procedures and manuals. Explicit knowledge implies declared knowledge (i.e., knowledge that is conscious to the knowledge bearer). Explicit knowledge is why it is not a problem for the employee to tell about rules and obviously learned facts. Very often this knowledge is already written down in books. Examples that contain explicit knowledge include NPP documentation and databases such as a website, an operational manual, records or a report of research findings.
+
−
 
+
−
'''Source: ''' [[Planning and Execution of Knowledge Management Assist Missions for Nuclear Organizations]]
+
−
 
+
−
==Description==
+
−
Explicit knowledge implies declared knowledge (i.e. knowledge that is conscious to the
+
−
knowledge bearer). Explicit knowledge is why it is not a problem for the employee to tell
+
−
about rules and obviously learned facts. Very often this knowledge is already written down in
+
−
books. The most important aspects of knowledge can be illustrated by using a knowledge
+
−
map. Such a tool is helpful in the transfer of knowledge from departing employees to their
+
−
successors (see Fig. 4).
+
−
[[File:Knowledgemap.PNG|thumb|right|500px|Fig. 4. Example of a simplified knowledge map]]
+
−
 
+
−
'''Source:''' [[Knowledge Management for Nuclear Industry Operating Organizations]]
+
  
 
==References==
 
==References==
−
 
  
 
==Related articles==
 
==Related articles==
Line 70: Line 46:
 
[[Tacit knowledge]]
 
[[Tacit knowledge]]
  
−
[[Information management]]
+
[[Documented knowledge lifecycle]]
  
−
[[Knowledge management]]
 
  
−
[[Category:Knowledge]]
+
[[Category:Knowledge type]]

Latest revision as of 14:38, 18 December 2015


Definition

Knowledge that has been articulated or has already been codified in some form

Summary

Explicit knowledge can be documented in useful forms such as operating manuals, files, reports, drawings, etc. Explicit knowledge can also be non-codified, but articulated and codifiable. There is much discussion about the distinction between information and explicit knowledge, but for practical purposes, here they will be used interchangeably.

Description

Explicit knowledge can be readily transferred to others.

The most common forms of codified explicit knowledge are documents, drawings, calculations, icons, designs, multimedia, databases, taxonomies, knowledge maps documented procedures and manuals.

Non-codified explicit knowledge (i.e., knowledge that is conscious to the knowledge bearer) includes for example existing non-documented procedures in an organization.

There is much discussion about the distinction between information and explicit knowledge, but for practical purposes of managing these two (similarity of tools and methods), they will be used interchangeably here.

The object can be information or explicit knowledge, depending on the recipient. The next section illustrates this thin boundary.

Illustrative examples

  • Expert (rule-based) systems contain information that allow an independent person to act upon it - hence it is considered explicit knowledge
  • Without an expert, NPP documentation will not allow an independent person to build and run an NPP - hence it is information
  • Power failure in an NPP is information for the general public (meaning: not able to operate), but knowledge for the operators (meaning:danger)

References

Related articles

Knowledge

Implicit knowledge

Tacit knowledge

Documented knowledge lifecycle

Retrieved from "http://wiki-nkm.iaea.org/wiki/index.php?title=Explicit_knowledge&oldid=15871"