AKTors.org
AKTors.org AKTTechnologiesPublicationsRelated ProjectsPeople
AKTors.org AcquisitionModellingRetrievalReusePublishingMaintenance
Automatic Support for Enterprise Modelling and Workflow from University of Edinburgh

Figure 1: A Holistic Support Framework for Informal Modelling Activities


Automatic Support for Enterprise Modelling and Workflow fact-file

Owner  :  University of Edinburgh
Researchers
(listed alphabetically)
 :  Jessica Chen-Burger [Browse, RDF]
Description  :  http://www.aiai.ed.ac.uk/%7Ejessicac/project/2-workflow-tech-profile-sub/details.html
Screencam  :  http://www.aktors.org/technologies/workflow/movie/kbst-em-movie.zip
Addresses challenges  :  Knowledge Acquisition, Knowledge Modelling, Knowledge Maintenance, Knowledge Reuse

What's the Problem?

  • Enterprise Modelling (EM) methods are well recognised for their value in describing complex domains in an organised but usually informal structure. Because of their lack of formal structure, the use of Enterprise Models that have been developed is limited.
  • Domain experts are normally not knowledge modellers and need to be assisted with automatic facilities to help them refine, verify, validate and share their models.
  • Collaborative knowledge work in real organisations may use different (informal) models to capture their group memory, consensus and visions. These models need to be shared and reused correctly to allow effective communication and learning. However, because of the informal nature of such models not all information has been shared effectively. When models are not being described formally, there may not be adequate facilities to support the exchange of information and ensure the consistency between different models.[10]
  • Business process modelling techniques provide rich conceptualisations that tend to describe the type of information required by the adaptive workflow systems. However, to achieve more widespread application, Workflow Management Systems (WfMS) need to be developed to operate in dynamic environments where they are expected to ensure that users are supported in performing flexible and creative tasks while maintaining organisational norms. Unfortunately, such needs have not been fully addressed.

Towards a Solution

Providing a Holistic Support Framework for Informal Modelling Activities

We propose a holistic supportive modelling framework to assist informal modelling that may be applied throughout its design-build-test-refine-use lifecycle. The framework is under-pinned by formal methods and illustrated in Figure 1 (above).

To support the building of enterprise models, an iterative cycle of knowledge-based support may be provided. KBST-EM is a generic modelling system that has been built on top of Hardy - a programmable hypertext-diagram tool that has been built in AIAI. Below is a list of example support facilities that are provided by KBST-EM (Knowledge Based Support Tool for Enterprise Modelling) and a workflow engine:

  • Method-specific model creation and documentation; [1][7][8]
  • Generic and method-specific knowledge based analysis, error detection and correction advise giving; [1][7][8][10]
  • Ontology based knowledge sharing between multiple models where each model may be described using different modelling methods; [2][4][9]
  • Dynamic behaviour illustration through state-stepping; [1][7][11]
  • Case-based retrieving and reuse of history models; [1][6]
  • Automatic translation to a different modelling language; [1]
  • When the enterprise model is a process model, the process mode may be used as a blueprint to automatically generate or modify a workflow system that implements the process model in real life. Figure 1 shows workflow systems J and K operating as agents in a distributed environment. [8][9][11]

Currently, 29 different modelling methods are supported by the KBST-EM and around 40 models are stored in the KBST-EM. Under the AKT project, two new methods were devised, AKT research map [3] and FBPML [5][8][9] and five new models have been developed. In KBST-EM, all modelling methods are supported with generic knowledge based support, and some of them also have method-specific facilities.

Figure 2 is a screen shot of KBST-EM. It shows a part of the ontology that has been used in the application domain of PC Configuration that is a part of the AKT work item: KRAFT-IX TIE (see KRAFT-IX TIE technology profile web page for more details).


Figure 2: Partial Ontology in the PC Configuration domain (KBST-EM screen shot)

Figure 3 shows another screen shot of KBST-EM which is part of a process model. This process model is written in FBPML (Fundamental Business Process Modelling Language) that has been developed as a part of AKT.


Figure 3: Process Model for PC Configuration Application

Knowledge Sharing and Inconsistency Checking between Multiple Models

To support knowledge sharing and improve consistency between models, an ontological mapping framework has been devised to enable the mapping between primitives of different modelling methods and concepts that have been captured in different models. Figure 4 shows an ontology based framework that shows how knowledge may be shared between different models.[4]


Figure 4: A common ontology captures the concepts that are being shared between different models

Figure 5 below gives an example where the same and similar information has been captured in different types of models, i.e. the process, data and business-view oriented models. These characteristics enable common knowledge to be shared between different models, and can be used for consistency checking of different models. This technique is based on knowledge about the different modelling primitives in different models and the underlying ontology that matches similar concepts, as suggested earlier in Figure 4.


Figure 5: The same and similar information are often captured in different types of models, but described in different form

Through the underlying shared ontology of all three models, it can be derived that D1, D1' and D1'' are compatible, and that O1, O1' and O1'' are compatible. When this technique is repeatedly applied, parts of different models can be mapped to each other. Below is an example of consistency checking axiom that makes use of the common ontology.

Support for Workflow System development: From design of process models to generation of workflow systems

Figure 3 gave a graphical description of a process model using FBPML notation [5][8]. Since FBPML has declarative execution semantics for processes, process models written in FBPML give precise instructions for implementation of a workflow system. Given a set of workflow functions that implement the corresponding components that are included in the FBPML process model, a workflow engine interprets the process model (against dynamics in the world) and invokes the appropriate functions for execution. Figure 6 gives the overall architecture of a workflow engine. More details are given in [8].


Figure 6: Overall Architecture of Workflow Engine

Take a Guided Tour

Example Applications

  • Virtual organisation communication and collaboration
  • Workflow applications
  • E-Business applications
  • Agent based systems collaboration

Further Reading

Example Key documents

Other relevant documents

Semantic representation

View in the AKT Triplestore Browser or as RDF.

Also available in DOAP RDF (Description Of A Project)