<!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>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Flavio Corradini</string-name>
          <email>flavio.corradini@unicam.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Luca Mozzoni</string-name>
          <email>luca.mozzoni@studenti.unicam.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jessica Piccioni</string-name>
          <email>jessica.piccioni@unicam.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Barbara Re</string-name>
          <email>barbara.re@unicam.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lorenzo Rossi</string-name>
          <email>lorenzo.rossi@unicam.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francesco Tiezzi</string-name>
          <email>francesco.tiezzi@unifi.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>BPMN collaboration, Physical Environment</institution>
          ,
          <addr-line>Modeling, Animation</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dipartimento di Statistica</institution>
          ,
          <addr-line>Informatica, Applicazioni</addr-line>
          ,
          <institution>University of Florence</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>School of Science and Technology, University of Camerino</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Nowadays, BPMN is a de-facto standard for modeling multiple participants processes as collaboration diagrams. BPMN collaboration can be heavily influenced by the physical environment in which the involved participants act. Indeed, they can occupy a position, move in the space, make decisions according to the environment's status, and change it. However, BPMN lacks support for integrating the environment. To overcome this limitation, we present BEAR, a tool for modeling and animating together a BPMN collaboration and its environment in the form of a place graph. BEAR supports designers in precisely understanding the interplay between BPMN collaborations and the environment.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Business Process Model and Notation (BPMN) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] has become a widely adopted standard for intuitively
and expressively modeling business processes. Particularly, BPMN collaboration diagrams are very
efective models for showing how participants e.g., humans, software systems, robots, and IoT devices,
behave and interact by exchanging information to achieve a common objective [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        The collaboration execution often depends on its working physical environment, in particular
on the topology of the space and the environmental attributes, e.g., temperature, lighting, weather
conditions, and network connectivity. Thus, in modeling such collaborations, it is crucial to consider
the environment where participants operate [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Indeed, participants can occupy a position, move, and
react to a particular environmental status. At the same time, activities, decisions, and events within a
process can depend on environmental conditions and change the environmental status.
      </p>
      <p>
        In this regard, the literature increasingly deals with the environment concept within BPMN [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ].
It focuses mainly on the efect of the environment on process execution while leaving the influence
of process activities on the environment underspecified. Diferently, in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], we discuss such interplay,
prescribing place graphs [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and place attributes as an abstraction of the physical environment where
the collaborations occur. We link the place graphs concepts with the BPMN meta-model, resulting in
the definition of environmental BPMN collaboration diagrams, and we equip such models with formal
operational semantics. Specifically, an environmental BPMN collaboration is the union of a BPMN
collaboration and a place graph.
      </p>
      <p>To enforce these findings and better guarantee a more precise understanding of the interplay between
BPMN collaboration and the environment, we propose BEAR (BPMN Environmental Animator). BEAR is
a novel BPMN animator tool that provides the user with a modeling environment to model environmental
BPMN collaborations and observe their execution through the flow of tokens over the diagram and the
evolution of environmental attributes.</p>
      <p>
        It is indeed well known from the literature that animator tools play an important role in easing the
understanding of the behavior of business processes [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In particular, diferent tools exist to model and
      </p>
      <p>CEUR</p>
      <p>
        ceur-ws.org
animate BPMN models. For instance, Allweyer and Schweitzer [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and Signavio [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] provide tools to
animate the control flow of BPMN processes; Corradini et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] propose the tool MIDA to animate
BPMN collaborations with multi-instance participants and data; Abdul et al. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] present UBBA that
creates and then animates a virtual 3D representation of a BPMN collaborations. Considering this
landscape of animator tools, BEAR is the only one implementing environmental aspects within the
BPMN notation.
      </p>
      <p>The rest of the paper is organized as follows. Section 2 describes the functionalities of the BEAR tool.
Section 3 assesses its maturity via case studies. Section 4 concludes the paper by providing links and
information about downloading, installing, and using BEAR.</p>
    </sec>
    <sec id="sec-2">
      <title>2. The BEAR tool features</title>
      <p>This section presents the BEAR tool and its features for supporting the understanding of the interplay
between collaboration business processes and the environment. BEAR provides modeling and animation
functionalities. The former allows the designer to create environmental BPMN collaboration diagrams,
while the latter is used to visualize the collaboration execution and the evolution of the environment.
The BEAR Modeler The interface of the BEAR modeler (Figure 1) is divided into two main parts i.e.,
the BPMN modeler on the left and the environment modeler on the right. The designer can use
the BPMN modeler to create a collaboration diagram using the standard elements and can exploit the
environment modeler to design a place graph representing the environment. A place graph consists of
nodes that symbolize a predefined area and edges that define the connection between them.</p>
      <p>In addition, using the button in the upper part of the interface, the designer can open the property
panel that appears in between the two modelers. By clicking an element from one of the modelers, the
property panel permits to add information related to the selected element and use them to drive the
animation. Starting from the place graph, the designer can insert a list of attributes characterizing the
environment in each place. These attributes are key-value pairs, e.g., alarm = false accessible by each
process in the collaboration by using the place name in front of the attribute name, e.g., place1.alarm.
All place attributes are accessible by the element of the BPMN collaboration in order to react and
change them. Similarly, the property panel shows for each BPMN element, beyond the already existing
properties like element name and identifier, it is possible to set new additional information related to
the interplay with the environment and to process data. In particular, selecting a pool element, we
added a new property called position that states the initial place of the participant represented by
the pool. This property appears in BEAR as a select box that lists all the place names in the place
graph. While selecting a data object, the designer can define process variables and instantiate them
with a value e.g., target = place1. Such data are accessible only by process elements of the same
pool like tasks, events, and gateways, making it possible to store, manipulate, and share information
also related to the environment. About tasks, the designer can specify (i) a guard condition, used to
constrain the execution of the task to specific values of data object and environmental attributes; (iii) a
list of assignments, used to modify the environment topology (by adding and/or deleting nodes and/or
places) or the values of data object and environmental attributes; and (iii) a destination, used to define
a place in the place graph to reach from the current participant position. The destination can be static
e.g., place1 or dynamic using a data object attribute valorized at run-time with a place name. If the
destination is null, the task does not involve any movement. For what concerns events the designer
can define message events (start, intermediate, end) with value passing. Specifically, send events can
exhibit a payload in the form of values e.g., "Payload" or 3; or attribute names e.g., place1.attr.
While receive events can exhibit an attribute name where to store the received payload. We also adopt,
conditional events (start and boundary) to which the designer can add a boolean condition used to
activate the event. A special condition for the conditional boundary event is the unreachability, used
to react in case the participant can not reach its destination. Finally, boolean expressions can be assigned
to the outgoing sequence flows of XOR gateways to drive decisions dynamically.</p>
      <p>
        The BEAR Animator The key characteristic of the BEAR Animator (Figure 2) is its dynamic visual
animation. It shows, in a step-by-step fashion, the evolution of the BPMN collaboration with its
environment. By selecting the Token Simulation in the BEAR interface, a play button will appear over
each fireable start event. Once this button is clicked, one process is activated. This creates a new token
in the form of a small colored circle at the start event of the BPMN process and another token in the
place of the place graph model corresponding to the value of the position property set on the pool.
Then, the token starts to cross the BPMN collaboration model and the environment model according to
the operational rules induced by our formal semantics [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. A Data Panel in the BEAR interface allows
the user to monitor the evolution of the values related to data objects and environmental attributes
during the animation.
      </p>
      <p>The animation terminates once all tokens cannot move forward. In case a token remains blocked
due to data object or environmental attributes valorization, e.g. a guard condition violation, BEAR
highlights it in red (Figure 2). Indeed, at any time, the animation can be paused by the user to check the
distribution of tokens in the environment and into the BPMN collaboration. From a practical point of
view, this allows designers to debug their environmental BPMN collaboration models. They can detect
undesired executions, where e.g. a control flow is blocked, and deduce the cause beyond it by possibly
checking the tokens marking the BPMN model and the place graph.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Maturity of the tool</title>
      <p>
        The BEAR tool is a web application written in JavaScript. It extends the bpmn-js1 toolkit and its token
simulation plug-in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. This makes BEAR accessible from any browser without a server backend,
and hence, it can be run in any operative system. To facilitate its usage, BEAR can be installed as a
Node application or a Docker container; moreover, we provide it online without the need to install any
software. By its nature, BEAR does not require significant computational power. Indeed, an animator
executes only a single run of the model using the input configuration, diferently from simulators and
model checkers that execute many runs of the same model, even all possible runs if necessary. For
this reason, BEAR performances are not afected by the dimension of the input environmental BPMN
collaboration diagram, and thus, it does sufer from scalability issues.
      </p>
      <p>
        To assess the maturity of BEAR, we designed and implemented eleven case studies belonging to
diferent application domains (e.g. agriculture, transport, restaurant, library, sale of products, and
logistics), three of which are inspired by the literature [
        <xref ref-type="bibr" rid="ref14 ref5">5, 14</xref>
        ]. We choose environmental BPMN
collaborations covering various dimensions, topology, and elements. The BPMN collaborations range
from 2 to 4 participants and from 11 to 53 elements. They are both structured and unstructured and
contain all the BPMN elements formalized in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The space models’ dimensions range from 11 places
and 22 transitions to 44 places and 150 transitions. Each case study comes with a short description and
two environmental BPMN diagrams, one is correct, i.e., the animation terminates without errors and
each process terminates successfully; the second contains a modeling error mentioned in the description
and verifiable animating it.
      </p>
      <p>The evaluation of these case studies has shown how environmental conditions can change the
outcome of the collaboration process. For the sake of presentation, we briefly discuss one of the case
studies concerning a fire-extinguishing collaboration in a student dormitory. The collaboration is
performed by a fire control system and a fire-fighting autonomous robot. The fire control system is in
charge of detecting fire in dormitory rooms through fire sensors and informing the extinguisher robot
that will reach the fire to extinguish it. The dormitory, inhabited by students, comprises a kitchen, an
entrance, three bedrooms, two bathrooms, and a living room connected by a corridor. Each room has a
door and a fire sensor. The collaboration starts when the fire control system detects the presence of fire
in one of the dormitory rooms. In this case, the fire control system notifies the fire-fighting robot of
the position of the fire and then activates the alarm. As soon as the robot receives the notification, it
moves toward the fire and, after extinguishing it, sends feedback to the control system, which turns of
the alarm. Notably, apart from the fire control system and the fire-fighting robot, some students in the
dormitory perform their daily routines interacting with the environment. Based on this scenario, the
BEAR animation can show two slightly diferent outcomes. Indeed, if the doors in the dormitory are
open, the fire-fighter can reach any place if the fire occurs. In the case the student closes a door, she/he
can make a room unreachable by the fire-fighter , which may be unable to extinguish the fire (Figure 3).
The environmental BPMN collaboration models exemplifying these two outcomes are made available
in the repository referenced in the next section.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Resources</title>
      <p>We provide the BEAR tool under the MIT license and in diferent forms, i.e., source code, online
service, and a Docker image. Moreover, we provide a detailed user guide explaining how to install
and use the tool, the environmental BPMN collaboration models and the description of each case
study. Finally, we provide a screencast showing the modeling and animation of the fire-extinguishing
collaboration described in Section 3. All the mentioned resources are available at https://pros.unicam.it/
environmental-bpmn/.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>OMG</surname>
          </string-name>
          ,
          <article-title>Business process model and notation</article-title>
          ,
          <source>BPMN V2</source>
          .
          <volume>0</volume>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C.</given-names>
            <surname>Muzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Pufahl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Weske</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tiezzi</surname>
          </string-name>
          ,
          <source>Formalising BPMN Service Interaction Patterns, in: The Practice of Enterprise Modeling</source>
          , volume LNBIP, Springer,
          <year>2018</year>
          , pp.
          <fpage>3</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>L.</given-names>
            <surname>Poss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schönig</surname>
          </string-name>
          ,
          <article-title>A generic approach towards location-aware business process execution</article-title>
          ,
          <source>in: Enterprise, Business-Process and Information Systems Modeling</source>
          , volume
          <volume>479</volume>
          <source>of LNCS</source>
          , Springer,
          <year>2023</year>
          , pp.
          <fpage>103</fpage>
          -
          <lpage>118</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Poss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Dietz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schönig</surname>
          </string-name>
          , Labpmn:
          <article-title>Location-aware business process modeling and notation</article-title>
          ,
          <source>in: Cooperative Information Systems</source>
          , volume
          <volume>14353</volume>
          , Springer,
          <year>2024</year>
          , pp.
          <fpage>198</fpage>
          -
          <lpage>216</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>R.</given-names>
            <surname>Saddem-Yagoubi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Poizat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Houhou</surname>
          </string-name>
          ,
          <article-title>Business processes meet spatial concerns: the sbpmn verification framework</article-title>
          ,
          <source>in: Formal Methods</source>
          , Springer,
          <year>2021</year>
          , pp.
          <fpage>218</fpage>
          -
          <lpage>234</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>F.</given-names>
            <surname>Corradini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Piccioni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Re</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tiezzi</surname>
          </string-name>
          ,
          <article-title>On the interplay between bpmn collaborations and the physical environment</article-title>
          ,
          <source>in: BPM2024</source>
          , Springer,
          <year>2024</year>
          . To Appear.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>I.</given-names>
            <surname>Afyouni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ray</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Christophe</surname>
          </string-name>
          ,
          <article-title>Spatial models for context-aware indoor navigation systems: A survey</article-title>
          ,
          <source>Journal of Spatial Information Science</source>
          <volume>1</volume>
          (
          <year>2012</year>
          )
          <fpage>85</fpage>
          -
          <lpage>123</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>I.</given-names>
            <surname>Maslov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Poelmans</surname>
          </string-name>
          ,
          <article-title>Facilitating the comprehension of business process models for unexperienced modelers using token-based animations</article-title>
          ,
          <source>Information and Management</source>
          <volume>61</volume>
          (
          <year>2024</year>
          )
          <fpage>103967</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>T.</given-names>
            <surname>Allweyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schweitzer</surname>
          </string-name>
          ,
          <article-title>A Tool for Animating BPMN Token Flow</article-title>
          , in: Int. Workshop on BPMN, volume
          <volume>125</volume>
          <source>of LNBIP</source>
          , Springer,
          <year>2012</year>
          , pp.
          <fpage>98</fpage>
          -
          <lpage>106</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>S. GmbH</surname>
          </string-name>
          , Signavio,
          <year>2018</year>
          . URL: http://www.signavio.com/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>F.</given-names>
            <surname>Corradini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Muzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Re</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tiezzi</surname>
          </string-name>
          ,
          <article-title>Formalising and animating multiple instances in bpmn collaborations</article-title>
          ,
          <source>Infomation Systems</source>
          <volume>103</volume>
          (
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>B. M.</given-names>
            <surname>Abdul</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Corradini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Re</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tiezzi</surname>
          </string-name>
          ,
          <article-title>Ubba: unity based bpmn animator</article-title>
          ,
          <source>in: CAiSE Forum</source>
          , volume
          <volume>350</volume>
          <source>of LNBIP</source>
          , Springer,
          <year>2019</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>P.</given-names>
            <surname>Fromme</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Warnke</surname>
          </string-name>
          , P. Dehn, bpmn-js
          <source>token simulation</source>
          ,
          <year>2017</year>
          . URL: https://github.com/bpmn-io/
          <article-title>bpmn-js-token-simulation.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>F.</given-names>
            <surname>Corradini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pettinari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Re</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Rossi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Tiezzi</surname>
          </string-name>
          ,
          <article-title>A technique for discovering bpmn collaboration diagrams</article-title>
          ,
          <source>Software and Systems Modeling</source>
          (
          <year>2024</year>
          )
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>