Difference between revisions of "Retention"
| Line 36: | Line 36: | ||
==Sub-processes== | ==Sub-processes== | ||
| − | + | There are no sub-processes for this knowledge process. | |
==Connection to other main categories== | ==Connection to other main categories== | ||
| − | To see how this [[Knowledge process|process]] is connected to KM challenges, benefits and tools, please refer to [[Portal: | + | To see how this [[Knowledge process|process]] is connected to KM challenges, benefits and tools, please refer to [[Portal:Maintenance]]. |
==Contribution to the management system== | ==Contribution to the management system== | ||
===Recommendation=== | ===Recommendation=== | ||
| − | |||
===Table of business processes=== | ===Table of business processes=== | ||
This [[Knowledge process|knowledge process]] is embedded in the following [[Business process|business processes]] in the [[Integrated management system]]. Each process has a score commensurate with its relevance to this process. | This [[Knowledge process|knowledge process]] is embedded in the following [[Business process|business processes]] in the [[Integrated management system]]. Each process has a score commensurate with its relevance to this process. | ||
| Line 51: | Line 50: | ||
! Business process !! Impact | ! Business process !! Impact | ||
|- | |- | ||
| − | ||[[Configuration management]]|| | + | ||[[Configuration management]]|| ? |
|- | |- | ||
| − | ||[[Technical skill resources]]|| | + | ||[[Technical skill resources]]|| ? |
|- | |- | ||
| − | ||[[Lessons learned]]|| | + | ||[[Lessons learned]]||? |
|- | |- | ||
| − | ||[[Information technology]]|| | + | ||[[Information technology]]|| ? |
|- | |- | ||
| − | ||[[Operating experience]]|| | + | ||[[Operating experience]]|| ? |
|- | |- | ||
| − | ||[[Peer review]]|| | + | ||[[Peer review]]|| ? |
|- | |- | ||
| − | ||[[Technology development]]|| | + | ||[[Technology development]]|| ? |
|} | |} | ||
==Processes not in the management system== | ==Processes not in the management system== | ||
| − | |||
==KM tools== | ==KM tools== | ||
| − | For all the KM tools that help implement the knowledge process see [[:Category: | + | For all the KM tools that help implement the knowledge process see [[:Category:Maintenance process tools]] |
==Case studies== | ==Case studies== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==References== | ==References== | ||
| − | |||
==Related articles== | ==Related articles== | ||
| − | [[Portal: | + | [[Portal:Maintenance]] |
| − | [[:Category: | + | [[:Category:maintenance processes]] |
[[Knowledge process (disambiguation)]] | [[Knowledge process (disambiguation)]] | ||
| − | [[:Category: | + | [[:Category:Maintenance process tools]] |
[[Category:Knowledge processes]] | [[Category:Knowledge processes]] | ||
| − | [[Category: | + | [[Category:Maintenance processes]] |
Revision as of 15:35, 14 June 2014
Template:Comment Template:Zoltan Template:DavidBeraha
,
Contents
Definition
Retention is The process of keeping knowledge in an organization
Summary
Knowledge retention relates to keeping explicit and tacit knowledge in the organization, usually on long term. Retaining tacit knowledge may focus on capturing tacit knowledge, usually a very difficult task, or trying to retain people with the requested knowledge in the organization. A re-hire program for retirees may yield significant benefits. Long-term storage of explicit knowledge requires robust and reliable devices to meet archiving requirements.
Retention belongs to maintenance processes.
For the nine main knowledge process categories see Fig 1.
Purpose
To keep knowledge in an organization.
Sub-processes
There are no sub-processes for this knowledge process.
Connection to other main categories
To see how this process is connected to KM challenges, benefits and tools, please refer to Portal:Maintenance.
Contribution to the management system
Recommendation
Table of business processes
This knowledge process is embedded in the following business processes in the Integrated management system. Each process has a score commensurate with its relevance to this process.
| Business process | Impact |
|---|---|
| Configuration management | ? |
| Technical skill resources | ? |
| Lessons learned | ? |
| Information technology | ? |
| Operating experience | ? |
| Peer review | ? |
| Technology development | ? |
Processes not in the management system
KM tools
For all the KM tools that help implement the knowledge process see Category:Maintenance process tools
Case studies
References
Related articles
Category:maintenance processes
Knowledge process (disambiguation)
Category:Maintenance process tools
Description
Knowledge retention relates to keeping explicit and tacit knowledge in the organization, usually on long term.
Retaining tacit knowledge
The efforts to retain tacit knowledge are usually closely connected with the identification of critical knowledge and the analysis of the risk of knowledge loss. The means of retaining tacit knowledge are twofold: if possible, the knowledge may be captured (see the Capture-article for a description of methods) and the resulting documents stored in an appropriate repository, and/or transferred. This may go hand in hand with efforts to maintain people who have the requested knowledge in the organization. A good working environment as well as a reward and recognition system may persuade experts to remain in the organization. Strategies to re-engage retired experts, assigning them the task to transfer knowledge to younger staff, may yield significant benefits.
Retaining explicit knowledge
Document management systems and content management systems are widely used for storing information and documents. These repositories are efficient for handling a dynamically changing database, with frequent additions, changes, or deletions. For long-term storage however, robust and reliable devices are required for archiving purposes. Electronic or digital formats can be stored on hard discs, optical media (CD, DVD, etc.), streamers (magnetic tapes) and/or in a film library. These could be read-only or editable, full text or just abstracts. For information stored in databases, database design should consider ease of retrieval in the future using metadata, thesauri, taxonomies, ontology, etc. Integrated information systems provide interoperability of different knowledge formats, including text, data, drawings, videos, and/or 3-D models. The information can be classified by author, release number, date of production, subject and/or keywords. Computer aided metadata creation tools can also be used to create metadata automatically for knowledge resources. A combination of the following software/system tools can be used in the implementation of electronic or digital archives:
- Add-ons which provide archiving functionality for document and content management systems
- Commercial relational database management systems (RDBMS), such as ORACLE, MSSQL, SYBASE, etc.;
- Intranet technology;
- Custom in-house RDBMS systems;
- Open source RDBMS, such as MySQL.
Example
The IAEA’s International Nuclear Information System (INIS) [1] offers a very good example of data storage methods and tools.
References
[2] INTERNATIONAL ATOMIC ENERGY AGENCY, Comparative Analysis of Methods and Tools for Nuclear Knowledge Preservation, Nuclear Energy Series No. NG-T-6.7 STI/PUB/1494, 2011
