6. Fusion in knowledge generation.
Perhaps the most obvious are those that allow for the sharing of knowledge in the first place. It is only through the sharing of knowledge that we become aware of the gaps in our knowledge. In the case of many businesses and organizations it is critically necessary to be able to surface current knowledge and assumptions. It is particularly important to surface fundamental assumption (the tacit context within which the business operates), the unwritten rules of the organization. In many organizations there have been examples of traditional "knowledge" that has been handed down from one generation to the next. Sometimes this knowledge has been explicitly handed down in company manuals or in training sessions. More often than not, however, it has been embedded in company processes-hidden from view but very much there. Knowledge management tools can be used to surface this knowledge and make it available for critical scrutiny. The process of fusion, combining pieces of information to produce higher-quality information, knowledge, and understanding, is often poorly represented in constructive models and simulations that are used to analyze intelligence issues. This report describes one approach to capturing the fusion process in a constructive simulation, providing detailed examples to aid in further development and instantiation. The sequential fusion method in intended to determine whether separate intelligence observations are close enough geographically, have consistently identified the same battlefield entity, and contain high-quality information, all of which must be considered before fusion of intelligence can occur. The fusion process described in this report is, for the most part, an implicit representation of the generation of battlefield intelligence and can be used in a constructive simulation or fusion model to better understand the dynamics of intelligence-gathering systems and their effect on intelligence metrics.
7. Mapping and modeling knowledge.
Well let’s assume you need to educate a team of professionals in some new software update, what is generally done is that they are filled into a classroom and someone walks in with a PPT or Document trains them and walks out assuming that all have been updated with the knowledge and all are educated.
Now, what knowledge mapping does is helps you identify/analyze each activity that needs to be done during training or any knowledge related activity, you need to document each and every step and look closely to find that if you teach this what is the ultimate result............... will they learn faster if not the what is the better alternative............. how do I test that they have learned.......you document/map the entire activity end to end right from the moment the plan of education is conceived to the time when you are going to conduct skill assessment.
Knowledge modeling is a process of creating a computer interpretable model of knowledge or standard specifications about a kind of process and/or about a kind of facility or product. The resulting knowledge model can only be computer interpretable when it is expressed in some knowledge representation language or data structure that enables the knowledge to be interpreted by software and to be stored in a database or data exchange file.
Knowledge-based engineering or knowledge-aided design is a process of computer-aided usage of such knowledge models for the design of products, facilities or processes. The design of products or facilities then uses the knowledge model to guide the creation of the facility or product that need to be designed. In other words it used knowledge about a kind of object to create a product model of an (imaginary) individual object. Similarly, the design of a particular process implies the creation of a process model, which design activity can be guided by the knowledge that is contained in a knowledge model about such a kind of process. The resulting process model, product model or facility model is typically also stored in a database.
Knowledge modeling includes the explication of knowledge and requirements that is available in documents, such as design manuals, (international) standard specifications and standard data sheets. In order to make such knowledge computer interpretable it need to be expressed in a formal knowledge representation language and thus transformed into a computer interpretable form. For example in the form of an expressions Gellish English. This enables that the knowledge and requirements are related to the objects in the knowledge model, whereas the whole model is again stored in a Database.