On Active Knowledge Modelling

The purpose of this paper is to highlight and explain the basic concepts and constructs of Active Knowledge Modelling (AKM) and how these concepts can be used to model work i.e. the activities we design, perform and manage to produce desired enterprise outcomes. 

In most cases models of work describe the activities or tasks needed to achieve the intended outcome. Present models are mostly activity charts and swim-lane diagrams. The problem with these models is that they do not consider the properties of the design and production of end products, nor the capabilities and workspaces required for operations of the product.

AKM addresses these shortcomings by facilitating modeling of multiple approaches and solution alternatives. AKM starts with modelling of the properties and product structures that shape the outcomes and targets, and create business values. From this knowledge base the activities and workspaces needed by designers, engineers, producers and service providers are identified, developed and coordinated. 

AKM also recognizes that the real world is built of endless chains of activities, dependencies, causes and effects. What is one party’s product is often defined by properties that are calculated in other party’s products. Think of a car or a plane composed and constructed from multiple products with similar properties that in themselves are sophisticated products (drive train, seating, suspension and chassis, …).

AKM can develop sets of use-case concepts derived from a generic meta-model, the IRTV model, i.e. the relationships between Information (products, outcomes, properties and parameters), Roles, Tasks and Views. The hard part is to go from these relatively abstract concepts to support of practical solutions for product design and manufacturing activities. The logic and context richness of practical workspaces must be modelled to form the knowledge base required for model-generated solutions and workplaces.

One of the cruxes in AKM modelling is Property objects. Outcomes and products are defined by modelling properties, their parameters and objects. Properties are assigned to roles responsible for property satisfaction, modelling and exploitation, and they are shared and balanced by parameter value views. Modelling collaborating roles and their workspaces is key to future benefits from digitalization, technical innovations, and practical collaboration.