strukt—A Pattern System for Integrating Individual and Organizational Knowledge Work

Abstract

Abstract. Expert-driven business process management is an established means for improving efficiency of organizational knowledge work. Implicit procedural knowledge in the organization is made explicit by defining processes. This approach is not applicable to individual knowledge work due to its high complexity and variability. However, without explicitly described processes there is no analysis and efficient communication of best practices of individual knowledge work within the organization. In addition, the activities of the individual knowledge work cannot be synchronized with the activities in the organizational knowledge work. Solution to this problem is the semantic integration of individual knowledge work and organizational knowledge work by means of the patternbased core ontology strukt. The ontology allows for defining and managing the dynamic tasks of individual knowledge work in a formal way and to synchronize them with organizational business processes. Using the strukt ontology, we have implemented a prototype application for knowledge workers and have evaluated it at the use case of an architectural office conducting construction projects.

The semantic web

“…In the knowledge engineering community the idea of task ontologies was first developed in order to automate knowledge processing. With Strukt [11] we gave an example of a task ontology developed in order to define human tasks. Core was the idea that ontologies and human processing tasks should be formally connected in a way that gives the human user maximal flexibility while still enforcing desired guarantees (e.g.…”

User Guidance for Document-Driven Processes in Enterprise Systems

“…Figure 2 sketches a preliminary view on the planned artifact. It is inspired by prior work on capturing and sharing best-practices in knowledge intensive activities and synchronizing them with the organizational business processes [18].…”

“…To modify the processes, the users can add new or change or delete existing activities. A key feature of our software artifact will be that such modifications during the execution of a process do not affect other concurrently executed processes [18]. Finally, the modifications made by the users can be incorporated again as best-practices and thus shared and communicated with the co-workers.…”