Scribd
Upload
236 views

Adaptive Process Management - Joining Process Model With Everyday Work Routine

1) The approach aims to make business process models more agile and flexible by combining top-down and bottom-up process modeling. 2) It does this by linking each process task to a task pattern that collects resources and experiences from previous executions to help guide future instances of that task. 3) Over time, as more adaptations are made by users and stored in the task pattern repository, the process models can be continuously tuned and evolved to better reflect how the processes are actually executed.

Uploaded by

Andreas Schmidt
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
236 views

Adaptive Process Management - Joining Process Model With Everyday Work Routine

1) The approach aims to make business process models more agile and flexible by combining top-down and bottom-up process modeling. 2) It does this by linking each process task to a task pattern that collects resources and experiences from previous executions to help guide future instances of that task. 3) Over time, as more adaptations are made by users and stored in the task pattern repository, the process models can be continuously tuned and evolved to better reflect how the processes are actually executed.

Uploaded by

Andreas Schmidt
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MATURE

Adaptive process management


Joining process model with everyday work routine

Agility has emerged as an important common characte- tened. Process activities are presented to a user in a way
ristic of successful businesses. Organisations of any size that allows for individual adaptations. Any changes or
benefit from quick response to volatile markets and enhancements to the process activities are documented
rapid changing user requirements. Conventional busi- and monitored. The advantage is two-fold: i) process-re-
ness process modelling and execution approaches have lated valuable resources and experiences are proactively
found themselves overstretched in such situations due presented to the others in the right context; ii) when suf-
to the lack of flexibility and the amount of overhead re- ficient adaptation information are accumulated, we can
quired for predefined process models. decide whether or not to tune process models against
the reality of actual process executions.
The Approach
Supporting knowledge workers in sha- Foundation
ring process-related knowledge and Continuous tuning and adapting busi-
refining processes ness process models
The approach is based on the insight that traditional Continuous tuning and adaptation of business process
“top-down” business process modelling approaches are models is facilitated through monitoring and analysing
too rigid and inflexible to capture the actual way pro- task patterns. We leverage the activities of a process mo-
cesses are executed while pure “bottom-up” approaches del to attach pertinent knowledge and experience to
may easily lose the focus and the alignment with orga- a process, via a one-to-one relationship between task
nisational goals. Therefore, business process models are patterns and activities. That is for each activity, the cor-
made agile and open by a joint hybrid approach. responding task pattern collects all the information that
In order to achieve this vision, the strict distinction is necessary for users to work on a concrete instance of
between build time and run time operations are sof- the activity, e.g. attached resources, comments on an is-

Top-down Hybrid Bottom-up

End-user
empowered
Expert-driven Or: automatic
Once-and-for-all (process) mining

Contact: Scientific Coordinator Andreas Schmidt, [email protected] - http://mature-ip.eu


sue, or problems and
solutions. When the
process is actually
executed, existing Business process model
task patterns (e.g. P) Concretise
will be retrieved from
a pattern reposito- Task pattern
ry. The system helps
users to populate P
by recommending Shared Shared
candidate resources resources experiences
to be used when
executing a task. Task pattern repository
Retrieve
Upon finishing, the
user can share her
task adaptation with Task Publish/Share
others by publishing
it back to the task
pattern repository. Task-specific Personal
resources experiences
The initial pattern Task-Pattern
should be thought Management System
of as a seed that
triggers the process
of attaching experience to a work context. These initial
Facts
patterns are meant to grow larger while we learn more
about the activities and mature over time adapting
to the actual way in which the process is executed in Features
practice. Maturing of task pattern indeed reflects back • Flexible automatic task assignment
to evolve the process models according to the needs in • End user involvement in process modelling and
practice. This is done by analysing adaptations made by evolution of process-related artefacts
individual users and stored in the task pattern reposito-
• Process/task-centred knowledge structuring and
ry. In addition the system based selection of knowledge
knowledge sharing
intensive activities will be mined to answer questions
such as “how often has one activity been chosen?”; “has • Adaptive process modelling through process mi-
this selection been appropriate?”; etc. ning and usage monitoring
Technology
The front-end of Demonstrator 4 (D4) is provided through
a semantic desktop application featuring resource
gathering and recommendation. Task patterns are
modelled and stored in the Semantic Media Wiki. Task-
related resources are collected in an RDF repository. The
D4 back end is supported by ontology-based business
process models constructed in a semantic modelling
environment, e.g. ATHENE, which, when executing, are
translated into a process execution language, e.g. BPEL or
XPDL, so as to work with workflow engines.
Contact
SAP Research
Hans-Friedrich Witschel,
Email: [email protected]
FHNW - University of Applied Sciences Northwestern
Switzerland
Barbara Thönssen
Email: [email protected]

Contact: Scientific Coordinator Andreas Schmidt, [email protected] - http://mature-ip.eu

You might also like