<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Discovering Organizational Perspective in Workflow using Agent Approach: An illustrative Case Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mahdi ABDELKAFI</string-name>
          <email>mahdi.abdelkafi@hotmail.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lotfi BOUZGUENDA</string-name>
          <email>lotfi.Bouzguenda@isimsf.rnu.tn</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>MIRACL Laboratory / ISIMS</institution>
          ,
          <addr-line>Route de Tunis, km 10. BP 242, 3021 Sakeit Ezzit, Sfax</addr-line>
          ,
          <country country="TN">Tunisia</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2010</year>
      </pub-date>
      <fpage>84</fpage>
      <lpage>98</lpage>
      <abstract>
        <p>The existing Workflow Management Systems, WfMS (ACTIONTm, Xsoft InConcert, Team Ware) show some insufficient due essentially to two factors. First, the enterprises express a real need of WfMS that deal with flexible business processes. These later must adapt to the optimization of enterprises work methods and the evolution of their needs. Second, the enterprises also need of control mechanisms and modeling tools for their WfMS in order to design robust workflow models assuring an efficient and flexible processing of errors and exceptions of execution. In others words, the WfMS must deal with Workflow mining to support Business Processes Re-engineering (BPR). A BPR is a method to improve the effectiveness and efficiency of business processes. Existing propositions in the literature are rather dedicated to the process perspective mining and they neglect the discovering of organizational perspective although it is decisive for the enhancement of existing workflow or the proposing of a new Workflow. The paper addresses the workflow mining by considering the organizational perspective. By organizational perspective, we mean the organizational structures (Federation, Hierarchical, Market and so on) and interaction protocols (Contract net, Auction...) describing respectively the forms of work and the activities allocation process between actors. This paper defends the idea that organizational dimension in multi-agent system is an appropriate approach to discover this organizational perspective since it (i) provides inter-agents communication languages based on performatives which allow capturing the semantic of exchanges between actors, (ii) it introduces organizational structures to highlight the forms of work and (iii) it offers powerful interactions protocols which permit to identify the dynamic organizational structures. First, this paper proposes a Workflow log meta-model which extends the classical one. Then, it provides some algorithms to permit the discovering of the main organizational structures and interaction protocols. Third, it presents the Management process of Water distribution crisis case study to illustrate our approach. Finally, the paper describes the developed prototype, called DiscopFlow, in order to validate the proposed solution. Keywords: Interaction Protocols, Organizational Structures, Workflow log Meta-Model, Algorithms and DiscopFlow.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Workflow Mining Context. The Workflow is a key technology which automates
the coordination of activities composing business process [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. A Workflow
Management System, WfMS is a software which permits to define, implement and
execute one or several business processes. In order to support the
interoperability between WfMS, the WorkFlow Management Coalition, WFMC has defined
reference architecture [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The main component of this architecture is the
Workflow Enactment Service (WES) that manages the execution of business processes
and that interacts, on the one hand, with business processes (or workflows)
definitions, execution and monitoring components and on the other hand, with
external WES. The communication among the different components is supported
by five interfaces of which Interface 5 is of most interest to us. This interface
supports the connection between the WES and the monitoring tools.
Unfortunately, a good standard for this interface has never been proposed. In this
context, the Workflow Mining area has recently appeared and considered as a
new research domain. More precisely, the purpose of Workflow mining is to
analyze the Workflow log in order to discover the Workflow perspectives such as
the Organizational Perspective (OP), the Informational Perspective (IP) and
the Process Perspective (PP) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], which help the monitor to improve or
propose a new workflow. The OP has two objectives. First, it structures actors in
classes playing each one a specific role (for instance subordinate and chief roles
in simple hierarchical structure). A class is called an organizational structure
defining an interaction space between actors. Of course, each actor belongs to
its own organizational unit where it plays a predefined role. Second the
organizational perspective describes the allocation activities between actors according
to interaction protocols. In this paper we are interested to discover the
organizational structures and interaction protocols and not the concepts of classical
organizational model such as role, organizational unit, etc. The IP describes the
structure of forms, documents and data which are consumed and produced by
processes. The PP defines activities components, their coordination, information
and actors involved in each activity. This perspective refers to both the
organizational perspective, which defines and organizes the set of potential actors, and
the informational perspective, which allows access to the objects to be processed.
Most of the work deals with the discovery of process and/or informational
perspective(s) while few researches were investigated around the discovery of the
organizational perspective although it is decisive for the enhancement of existing
workflow or the proposing of a new Workflow ([
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]).
      </p>
      <p>A good application domain justifying the need to discover the organizational
perspective is that of crisis Workflows as much as it is important to understand
the social behavior of the actors during a crisis process. In others terms, we
need to know the involved organizational structures in this crisis and the
interaction protocols used by the potential actors.In this paper, we have chosen
the well-known ”Management process of Water Distribution crisis” case study
for three reasons. First, the water is a main need for the human and must be
protected against any incident. Second, the frequency of water pollution is very
high. Third, this case study is complete in so far as it illustrates clearly the
interaction protocols used by the actors (Analyst, Controller, Investigator and
so on) and the deployed organizational structures.</p>
      <p>
        The problem being addressed in this paper is how to discover the organizational
perspective from workflow log? We recall that organizational perspective refers
to the organizational structures and interaction protocols. One possible way to
deal with the discovering of organizational perspective in workflow is to use the
agent approach and more precisely:
– the FIPA-ACL performatives which define the semantic of messages and
notably the agents intentions,
– the interaction protocols such as contract net, auction and negotiation which
constraint the conversations between actors during the activities allocation,
– the organizational structures like coalition, hierarchical, market and federation
which define the behavior of actors ([
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
      </p>
      <p>The goal of this paper is to propose a Workflow log Meta-model to help the
discovery of organizational structures and interaction protocols.
Our solution is based on the following principles:
– The inclusion of the three complementary workflow perspectives. As a
consequence we can support any discovering of perspective.The use of FIPA-ACL
Performatives which are appropriates to define the organizational structures
referencing interaction protocols,
– The simplicity by including the basic workflow concepts.</p>
      <p>Organization of the paper. The reminder of this paper is organized as follow.
Section 2 motives the use of Agent approach for discovering organizational
structures and interaction protocols in Workflow. Section 3 describes the Workflow
log Meta-model that we propose to deal with organizational perspective mining.
Section 4 presents our case study useful for instantiating this model. First, it
introduces the Petri Nets with Objects formalism and exposes its three models
which are in interaction. Then, it gives the instantiated Meta-model. Finally, it
discusses some organizational structures and interaction protocols which can be
discovered according to this instantiation. Section 5 briefly discusses the related
Works and concludes the paper.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Motivations for using Agent Approach</title>
      <p>The objective of this section is to briefly motive the use of agent approach for
organizational perspective discovering in workflow and more precisely:
– the FIPA-ACL communication language,
– the organizational structures,
– the interaction protocols,</p>
      <p>
        FIPA-ACL (Foundations of Intelligent Physical Agents-Agent
Communication Language, http://www.fipa.org) is one of the inter-agents communication
languages proposed by the agent community. It is composed of a set of
performatives and integrating of protocols. The FIPA-ACL message structure is shown in
figure 1. For more information on FIPA-ACL performatives the interested reader
can refer to [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>(Performative
:sender A
:receiver B
:content XXX
:in-reply-to YYY
:language ZZZ
:reply-by CCC
:conversation_ID VWV)</p>
      <p>These FIPA-ACL performatives play a key role in the activities allocation
between actors. First, they clearly define the semantic of messages and namely
the agents intentions (delegate, subcontract, negotiate,). Second, they highlight,
during the interaction between agents, the organizational structures such as
coalition, sub contracting, federation and so on. Third, they capture without
ambiguity the interaction protocols like contract-net, auction, negotiation and
heuristic. These interaction protocols could be used with benefits to allocate
activities to actors in workflow. The table 1 describes the performatives used in
this paper.</p>
      <p>The organizational structures mentioned above can model the behaviour of
the systems under consideration. I.e. they describe the macro-level dimension
of the coordination among actors in terms of externally observable behaviour,
independently of the internal features of each participating component.</p>
    </sec>
    <sec id="sec-3">
      <title>3 The Workflow log Meta-model</title>
      <sec id="sec-3-1">
        <title>3.1 Key requirements for a Workflow log Meta-model</title>
        <p>The most important requirements for a Workflow log Meta model are the
following:
Performative Description
Delegate The initiator delegates the receiver the Activity A of Case C
Inform Concerns any information dispatch concerning Activity A of</p>
        <p>Case C
Execute The initator informs that it performed the Activity A of</p>
        <p>Case C
Call for Proposal Call for Offers: announces a negotiation for performing of the</p>
        <p>Activity A of case C
Propose The initiator proposes to execute an Activity
Refuse The initiator refuses the proposition of the receiver
Accept Proposal After propose: to mean the acceptation
Reject Proposal After propose: to mean the reject
– It must allow the expression of the three workflow perspectives such as the
informational perspective, the organizational perspective and the process
perspective,
– It must be simple and comprehensive: it must define the core concepts of the
three complementary Workflow perspectives,
– It supports the discovering of organizational structures and interaction
protocols without ambiguity as mentioned previously.</p>
        <p>
          Most of the work concerning Workflow perspectives mining ([
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]) only
focuses on the process perspective by providing a workflow log containing only
concepts of the process perspective. Other also considers the informational
perspective besides to the process perspective [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. To the best of our knowledge,
any work supports the last requirement and makes really the glue between the
three workflow perspectives. Consequently, we have defined our own meta-model
which fulfills the previous requirements. This meta-model is shown in the UML
diagram of figure 2.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 The proposed Workflow log Meta-model</title>
        <p>In this UML Meta-model, a Process is composed of one (or several) Process
Instance(s). Each Process Instance is composed of one (or several) Event(s).
Each Event makes reference to the following elements:
– An Activity which is described through the Act Name attribute,
– A Document which is described through the Doc Name attribute,
– An Actor which is described through the Actor ID and Actor Name attributes,</p>
        <p>Its a member of organizational unit and plays one (or several) Role(s),
– A Role which is described through the Role Name attribute,
– An Organizational Unit which is described through the Org Unit Name
attribute,
Process
Pro_Name
-Composed of</p>
        <sec id="sec-3-2-1">
          <title>1..* PProroc_eIsnss-_InIDstance</title>
          <p>Process
Perspective
Performative</p>
          <p>Perf_Name</p>
          <p>The process perspective is described with the Process Instance, Event and
Activity classes (or concepts). According to the literature, these concepts are
sufficient to discover the process structure. The informational perspective is
described with the Process Instance, Event and Document concepts. We have
chosen only to add the document concept because we think that this later will be
very useful in crisis process. It is important to know on what such actor is based
to produce such document. For instance, in our case study (Management Process
of Water Distribution Crisis) the Malik actor playing the penal role can produce
the document Juridical Report only on the basis of a document Investigation
Report produced by the Walid actor playing the investigator role (see figure 4).
The organizational perspective as mentioned in introduction is represented with
Actor, Role, Organizational Unit and Performative concepts.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 An illustrative case study</title>
      <p>The Objective of this section is (i) to illustrate the workflow log Meta-model
instantiation through the well-known Management process of Water Distribution
crisis case study and (ii) to show the organizational structures and interaction
protocols which can be discovered. First, it briefly introduces Petri Net with
Objects (PNO) formalism as an appropriate language for modelling processes.
Second, it models the case study through three communicating models (information,
organization and process). Third, it presents the instantiated Meta-Model.
Finally, it exposes some organizational structures and interaction protocols which
can be discovered.</p>
      <sec id="sec-4-1">
        <title>4.1 What are Petri Nets with Objects?</title>
        <p>
          Petri Nets with Objects (PNO) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] are a formalism combining coherently Petri
nets (PN) technology and Object-Oriented (OO) approach. While PN are very
suitable to express the dynamic behavior of a system, OO approach enables the
modeling and the structuring of its active (actor) and passive (information)
entities. In a conventional PN, tokens are atomic and undissociable, whereas they
are objects in a PNO. As any PN, a PNO is made up of places, arcs and
transitions, but in PNO, they are labeled with inscriptions referring to the handled
objects. More precisely, a PNO features the following additive characteristics:
– Places are typed. The type of a place is a (list of) type of some object-oriented
sequential languages. A token is a value matching the type of a place such as a
(list of) constant (e.g. 2 or hello), an instance of an object class, or a reference
towards such an instance. The value of a place is a set of tokens it contains. At
any moment, the state of the net, or its marking is defined by the distribution
of tokens onto places. A transition is connected to places by oriented arcs as
it aims at changing the net state, i.e. the location and value of tokens.
– Arcs are labeled with parameters. Each arc is labeled with a (list of) variable
of the same type, as the place the arc is connected to. The variables on the
arcs surrounding a transition serve as formal parameters of that transition and
define the flow of tokens from input to output places. Arcs from places to a
transition determine the enabling condition of the transition: a transition may
occur (or is enabled) if there exists a binding of its input variables with tokens
lying in its input places. The occurrence of an enabled transition changes
the marking of its surrounding places: tokens bound to input variables are
removed from input places, and tokens are put into output places according
to variables labeling output arcs.
– Each Transition is a complex structure made up of three components: a
precondition, an action and emission rules. A transition may be guarded by a
precondition, i.e. a side effect free Boolean expression involving input
variables. In this case, the transition is enabled by a binding only if this binding
evaluates the precondition to true. Preconditions allow for the fact that the
enabling of a transition depends on the location of tokens and also on their value.
Most transitions also include an action, which consists in a piece of code in
which transitions variables may appear and object methods be invoked. This
action is executed at each occurrence of the transition and it processes the
values of tokens. Finally, a transition may include a set of emission rules i.e.
side-effect free Boolean expressions that determine the output arcs that are
actually activated after the execution of the action.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2 The Informational Model</title>
        <p>The informational model that we propose focuses only on the documents
consumed or produced by the case study process (see figure 3). More precisely, it
contains the following documents:</p>
        <p>Quality Report
-ID
-Title
- Water Quality</p>
        <p>concernes
1. *</p>
        <p>Sample
-ID
-Site
-Date
used by</p>
        <p>Evaluation Sheet
-ID
-Description
gives rise to</p>
        <sec id="sec-4-2-1">
          <title>1. * -PIDlans of Ations</title>
          <p>-Description
Investigation Report
-ID
-City_Name
-Address of site
-Event
-Norm
-Perimeter-Security
-Date
used by</p>
          <p>Juridical Report
1. * -ID
used by -Description
• An Investigation Report which can be used by one or several Juridical Report,
• An Evaluation Sheet which is based on Quality Report and gives rise to one
or several Plans of Actions,
• A Quality Report concerns one or several Sample to be analysed.</p>
        </sec>
      </sec>
      <sec id="sec-4-3">
        <title>4.3 The Organizational Model</title>
        <p>Our organizational model is organized around the following components (see
figure 4).</p>
        <p>Thirteen roles:
• Investigator: Consists in elaborating an investigation report, informing the
penal and delegating the triggering of alarm to the reporter,
• Penal: Consists in elaborating the juridical report,
• Reporter: consists in informing the controller of the incident arrival,
• Controller: consists in realizing the taking of sample from the pumping site in
order to prepare the samples and delegate their analysis,
• Analyst: consists in analysing of samples, elaborating a quality report and
informing the authority to trigger the crisis cell,
• Authority: consists in activating and inactivating the pumping site,
• Evaluator: consists in informing the scheduler of the risks evaluation result,</p>
        <p>Quality
insurance</p>
        <p>CCrieslis OJrugraidniicsaml Government
OrganizationalUnit 1.*
Isa
member
• Scheduler: consists in informing the decider of the plans of actions,
• Decider: consists in validating one among proposed plans of actions,
• Distributor: consists in distributing of water bottles to the concerned users,
• Juridical expert: consists in validating the juridical report,
• Disinfector: Consists in cleaning the polluted site,
• Mediator: Consists in diffusing information to the concerned users.
Four organizational units:
• Quality insurance: charged to control the water quality,
• Crisis cell: charged to assure the return to the normal functioning of the Water
distribution system,
• Juridical Organism: charged to take the juridical decisions,
• Government: charged to activate/inactivate the pumping site.</p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4 The Process model</title>
        <p>The objective of the management process of Water Distribution crisis is to assure
the return to the normal functioning of the Water distribution system. More
precisely, this process is made of several coordinated activities and described using
Petri Nets with Objects (see figure 5). Let us detail the activities (transitions)
composing the process:</p>
        <p>Investigation report establishment (A1) is realized by the investigator and
consists in elaborating an investigation report containing all the information
around the incident, the security perimeters and transport norms.
Alarm triggering (A2) is realized by the reporter and consists in triggering an
alarm in order to inform the arrival of incident on water distribution system.
Juridical report establishment (A3) is realized by the penal and consists in
establishing a juridical report describing the juridical decisions.</p>
        <p>Juridical report Validation (A4) is realized by a juridical expert and consists in
applying the juridical decisions taken by the penal.</p>
        <p>Taking of samples (A5) is realized by a controller and consists in realizing
Taking of samples on water distribution system, preparing of samples and sending
them to the analysts.</p>
        <p>Analysis of samples (A6) is realized by an analyst and consists in handling the
samples and elaborating a quality report.</p>
        <p>Risks Evaluation (A7) is realized by an evaluator and consists in elaborating an
evaluation sheet containing the eventual risks.</p>
        <p>Actions scheduling (A8) is realized by a scheduler and consists in proposing more
actions plans to assure the return to the normal functioning of the water
distribution system.</p>
        <p>Actions plans validation (A9) is realized by the decider and consists in validation
of one actions plan.</p>
        <p>Disinfection of polluted site (A10) is realized by a disinfector and consists in
realizing the cleaning work on the polluted site.</p>
        <p>Information diffusion (A11) is realized by media (TV or Journal) and consists
in informing the concerned users.</p>
        <p>Inactivation of the site (A12) is realized by the authority and consists in
interdiction the functioning of the water distribution system.</p>
        <p>Water bottles distribution (A13) is realized by a distributor and consists in
distributing water bottles to the concerned users.</p>
      </sec>
      <sec id="sec-4-5">
        <title>4.5 The Instantiated Meta-Model</title>
        <p>In order to illustrate the Workflow log meta-model instantiation, we propose to
use the process model presented previously.</p>
        <p>This instantiation is visualized in figure 6.</p>
        <p>For instance, the grey part of this figure represents the contract net
protocol employed between actors Malik, Walid and Mahdi (see figure C in table
2). According to this protocol, Malik launches by a call for dealing with given
activity (Cfp). The other actors Walid and Mahdi propose their bid (Propose).
Finally, Malik notifies each participant either by acceptation (Accept-propose)
or by rejection (Reject-propose). This information is useful to understand how
to allocate activities to actors.</p>
      </sec>
      <sec id="sec-4-6">
        <title>4.6 The Organizational Structures and Interaction Protocols which can be discovered from our Workflow Log</title>
        <p>According to the instantiated meta-model, we give here some organizational
structures and interaction protocols that can be discovered. For each
organiza</p>
        <p>A5
&lt;Analyst&gt; &lt;Sample&gt;</p>
        <p>An S</p>
        <p>A6 QR=An.etablish()
&lt;Evaluator&gt; &lt;Quality Report&gt;</p>
        <p>Ev QR
A7 SE=Ev.Evaluate(QR)</p>
        <p>&lt;Evaluation Sheet&gt;
tional structure or interaction protocol we only give its definition and its
associated graphic representation.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5 Discussion and Conclusion</title>
      <p>
        The organizational perspective mining remains insufficiently addressed([
        <xref ref-type="bibr" rid="ref10">10</xref>
        ],
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]). Existing propositions in the literature are rather dedicated to the
process perspective mining([
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ])and they neglect the important point that
workflow is much more that process perspective. We believe that these works
      </p>
      <p>Process Instance
[Case 1,{E1,E2,E3, E4,. , E11, E12, E13, E14, E15, E16, E17},….]
[Case 2,{E20, E21, E23, E24,. .}, …. ]
[Case 3,{E41,E42,E43,. .}, …. ]</p>
      <p>Performative
[Execute,E1]
[Delegate,E2]
[Execute,E3]
[Inform, E4]
...
[Cfp, E11]
[Cfp, E12]
[Propose, E13]
[Propose, E14]
[Accept-propose, E15]
[Reject-propose, [E16]
[Execute, E17]</p>
      <p>Role
[{IDA1, Legal Juridical Organism},Investigator]
[{IDA2, Legal Juridical Organism}, reporter]</p>
      <p>Organizational Unit
[Legal Juridical Organism,{IDA1,IDA2,…}]
[Crisis Cel,{IDA6,IDA3,IDA8,…}]
[Quality Insurance,{IDA9,IDA10,IDA11,…}]</p>
      <p>
        Actor
[IDA1, Dupont, {E1,Execute}]
[IDA1, Dupont, {E2,Delegate}]
[IDA2, David,{E3, Execute}]
[IDA2, David,{E4,Inform}]
[IDA2, David, {E5,Delegate}]
[IDA2, David, {E6,Delegate}]
[IDA3, Mahdi, {E7,Execute} ]
[IDA4, Malik, {E8,Execute} ]
.ID….A.11, Malik, {E11, Cfp}]
IDA11, Malik, {E12, Cfp}]
[IDA12, Mahdi, {E13, Propose}]
[IDA13, Walid,{E14, Propose}]
IDA11, Malik, {E15,
Acceptpropose}]
IDA11, Malik, {E16,
Rejectpropose}]
IDA11, Walid, {E17, Execute}]
limit the scope and utility of workflow mining. For instance [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]only focuses on
process mining by providing a Workflow log meta-model which defines the
minimum concepts of process. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]proposes a statistical technique to discover
Workflow patterns from event log.[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]deals with the workflow mining in more workflow
perspectives (process and informational perspectives) but without consider the
organizational perspective.[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]defines three methods for mining of organizational
structures from workflow logs such as default mining, mining based on the
similarity of activities and mining based on the similarity of cases. Even if the
proposed solution in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]deals with the organizational perspective mining,it does
not exploit the agent approach and as a consequence it does not support the
interaction protocols and organizational structures so far discovered. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]proposes
an approach based on metrics expressing the relationships among actors deriving
social networks. We believe our solution is currently unique in trying to take into
account the three Workflow perspectives in unique model.
      </p>
      <p>In this paper, we have presented an approach based on agent technology to deal
with organizational perspective discovering.</p>
      <p>To better illustrate our solution, we have chosen the well-known Management
process of Water Distribution crisis case study.</p>
      <p>The proposed meta-model is characterized by:
– its inclusion of three complementary workflow perspectives and as a
consequence it supports any perspective discovering although in this paper we only
focus on the organizational perspective,
Organizational
Structure or
Interaction Protocol</p>
      <p>Definition</p>
      <p>Graphic representation
l
a
c
i
h
c
r
a
r
e
i
H
e
l
p
m
i
S</p>
      <p>It’s a flat hierarchy at
single level. A single
agent has the
authority to catch decision
while all other
members are his
subordinates.</p>
      <p>A federation is a
set of groups. Each
one is represented
by a delegate. This
later plays the role
of mediator between
its group and the
exterior.</p>
      <p>In the CNP, one
agent takes the
manager role which
desires to have one
or more agents (the
participants) to
execute some activities.</p>
      <p>Each participant
submits its bid. The
manger selects the
well offer and rejects
the others bids.</p>
      <p>A)
B)
C)</p>
      <p>Dupont</p>
      <p>David
Malik</p>
      <p>Wassim</p>
      <p>Walid
Crisis Cel</p>
      <p>Quality</p>
      <p>Insurance
Cfp (Initiator: Malik,
Receivers: Walid,Mahdi,
Activity: Distribution of</p>
      <p>water bottles)
Propose(Initiator: Mahdi,
Receiver: Malik,
Activity: Distribution of
water bottles)</p>
      <p>Propose(Initiator: Walid,
Receiver: Malik,
Activity: Distribution of</p>
      <p>water bottles)
Reject-Propose(Initiator: Malik,
Receiver: Mahdi,
Activity: Distribution of
water bottles)</p>
      <p>Accept-Propose (Initiator:Malik
Receiver: Walid,
Activity: Distribution of</p>
      <p>water bottles)
Inform(Initiator: Walid,
Receiver: Malik,
Activity: Distribution of
water bottles)
– its simplicity since it defines the core concepts of the three workflow
perspectives,
– and finally, it exploits the Agent technology concepts (organization
abstractions, FIPA-ACL performatives and interaction protocols) which ease the
organizational structures and interaction protocols mining.</p>
      <p>Actually, the DiscoopFlow (Discovering Organizational Structures and
Interaction Protocols in WorkFlow) prototype development is in progress.
We have implemented some algorithms for discovering organizational structures
like simple hierarchical and federation structures. The figure 7 gives an idea
about the overview of our prototype.</p>
      <p>As future work, we plan to implement the discovering algorithms concerning
interactions protocols and others organizational structures (market, multi-levels
hierarchical, etc.).</p>
      <p>We also aim to discover conjointly the three workflow perspectives in a coherent
framework and extend our Workflow Meta model by adding the intentional
perspective. We believe that this perspective justifies the choice of such execution
scenario for a given crisis process.</p>
      <p>Acknowledgment : The authors acknowledge all the participants involved in
the DiscoopFlow project development. More precisely, they acknowledge Foued
BEN MOALLEM, Achraf BOUDAWARA, Wassim CHTOUROU and Akram
BEN AMOR.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Workflow</given-names>
            <surname>Management</surname>
          </string-name>
          <article-title>Coalition.: The Workflow Reference Model</article-title>
          .
          <source>Technical Report WFMC-TC-1003</source>
          ,
          <string-name>
            <surname>November</surname>
          </string-name>
          (
          <year>1994</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Van</surname>
            <given-names>Dongen</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>BF.</given-names>
            ,
            <surname>Herbst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Maruster</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Schimm</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          , Weijters, AJMM.:
          <article-title>Workflow mining: A survey of issues and approaches</article-title>
          .
          <source>In Data &amp; Knowledge Engineering</source>
          , volume
          <volume>47</volume>
          (
          <issue>2</issue>
          ), pages
          <fpage>237</fpage>
          -
          <lpage>267</lpage>
          , (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Van</surname>
            <given-names>Dongen</given-names>
          </string-name>
          , BF., Van der Aalst, WMP.:
          <article-title>A Meta Model for Process Mining Data</article-title>
          .
          <source>In Advanced Information Systems Engineering</source>
          , volume (
          <volume>161</volume>
          ),(
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gaaloul</surname>
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Godart</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Mining Workflow Recovery from Event Based Logs</article-title>
          .
          <source>In 3rd international conference on Business Process Management</source>
          ,
          <string-name>
            <surname>BPM</surname>
          </string-name>
          , Nancy,(
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Workflow Mining of More Perspectives of Workflow. In Software Engineering and Applications,in SciRes (www</article-title>
          .SciRP.org/journal/jsea),Volume
          <volume>1</volume>
          ,
          <string-name>
            <surname>Pages</surname>
            <given-names>83</given-names>
          </string-name>
          <source>-87</source>
          , (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Agent</given-names>
            <surname>Communication</surname>
          </string-name>
          language Specifications. (http://www.fipa.org/repository/aclspecs.html).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Mathieu</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Routier</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Secq</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Dynamic Organization of multi-agents systems</article-title>
          . In proceeding of the first international joint conference on Autonomous Agents and
          <string-name>
            <surname>Multi-Agent</surname>
            <given-names>Systems</given-names>
          </string-name>
          , ACM Press, (
          <year>2002</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Koning, JL.,
          <string-name>
            <surname>Pesty</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Modles de communication.
          <article-title>Principes et architectures des systems multiagents</article-title>
          . Chapitre 3,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>Briot</surname>
          </string-name>
          , Y. Demazeau (eds), paris, Hrmes science publications, (
          <year>2001</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sibertin-Blanc</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>High Level Petri Nets with Data Structure</article-title>
          .
          <source>6th Int. Workshop on PetriNets and Applications Espoo (Finland)</source>
          ,(
          <year>1985</year>
          ) .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Gao</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zeng</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Le</given-names>
            <surname>Zhang</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Wang</surname>
          </string-name>
          , YW.:
          <article-title>Organizational Structure Mining Based on Workflow Logs</article-title>
          .
          <source>In International Conference on Business Intelligence and Financial Engineering</source>
          , Beijing, China,
          <source>July 24-July</source>
          <volume>26</volume>
          , (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Van der Aalst</surname>
            , W.
            <given-names>M.</given-names>
            P and Song, M.
          </string-name>
          :
          <article-title>Towards comprehensive support for organizational mining</article-title>
          .
          <source>In Decision Support Systems</source>
          , Volume
          <volume>46</volume>
          ,
          <string-name>
            <surname>Issue</surname>
            <given-names>1</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pages</surname>
            <given-names>300</given-names>
          </string-name>
          <source>-317</source>
          , (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>