<!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>Synthesis of Strategies for Robotic Process Automation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sapienza University of Rome</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy agostinelli@diag.uniroma</string-name>
        </contrib>
      </contrib-group>
      <pub-date>
        <year>2019</year>
      </pub-date>
      <fpage>16</fpage>
      <lpage>19</lpage>
      <abstract>
        <p>Robotic Process Automation (RPA) is an umbrella term for tools that run on an end user's computer, emulating tasks previously executed through a user interface by means of a software robot. Nowadays, only simple, predictable tasks can be automated in situations where there is no room for interpretation, while more sophisticated work is still left to human experts. The here proposed research aims at tackling this issue through a paradigm shift in conceiving software robots that are able to behave intelligently and exibly in many dynamic and knowledgeintensive situations that are common in today's application scenarios.</p>
      </abstract>
      <kwd-group>
        <kwd>Robotic Process Automation tion</kwd>
        <kwd>Process Mining</kwd>
        <kwd>Automated Planning</kwd>
        <kwd>Human Computer Interac-</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>all possible behaviours of a robot; and (iii) orchestrating the behaviours of single
robots in order to synthesize complex execution strategies able to emulate the
enactment not just of single tasks, but of interconnected and large work ows.
2</p>
    </sec>
    <sec id="sec-2">
      <title>State of the art</title>
      <p>
        Most of the actual deployments of RPA are industry-speci c, e.g., nancial and
business services [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], and the market for RPA solutions is developing rapidly.
Nowadays, robots are mainly used for automating repetitive o ce tasks in
operations like accounting, billing and customer service. Robots are capable of log
into applications, connect to system APIs, copy and paste data, extract
semistructured data from documents, read and write to databases, open e-mail and
attachments, ll in forms, make calculations, etc. Despite the capabilities of
software robots, the RPA technology is still in its infancy, even if similar solutions
have been around for a long time. For instance, closely related to software robots,
chatbots have been using for years to accept voice-based or keyboard inputs and
guide customers to nd relevant information in web-based applications [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
Differently from chatbots, RPA can be seen as an evolution of traditional screen
scraping solutions [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which sought to visualize screen display data from legacy
applications (having no means for automated interfacing) in order to display
such data using modern UIs. The strength of RPA is that it does not replace
existing applications or manipulate their code, but rather works with them in
a way similar to a human user. However, it is worth to notice that the current
generation of software robots is guided by procedural rules rather than AI. To be
more speci c, a software robot can be developed by a human designer through
a trial-and-error approach consisting of 2 steps that are repeated until success
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]:
{ First, the designer produces a owchart diagram that includes the single
actions to be performed by the robot on the UI to emulate a task of the
system.
{ Second, the designer checks if the robot's behaviour during the execution
of the task on the UI is capable to properly reproduce the behaviour of a
human user that executes the same task. If any misalignment exists, the
designer adjusts the owchart diagram to x the identi ed gap.
While this approach is particularly e ective for executing simple rules-based
logic in situations where there is no room for interpretation, it becomes
timeconsuming and error-prone in presence of tasks that are less predictable or
require some level of human judgment. As a consequence, RPA is not yet able
to fully replace human work. Only simple, predictable tasks can be automated.
In cases where the rule set does not contain a suitable response for a speci c
situation, robots allow for escalation to a human supervisor . This is
particularly true in today's application scenarios, where also predictable tasks become
less-predictable, due to the huge amount of data and events produced in these
contexts that may in uence their enactment.
      </p>
      <p>Flowchart diagrams</p>
      <p>Action1
Action2
Action3
Action1</p>
      <p>Action2
Action1</p>
      <p>Action2</p>
    </sec>
    <sec id="sec-3">
      <title>Research objectives and methodology</title>
      <p>This research falls within the scope of RPA, and its overall objective is to devise
an approach to automatically synthesize intelligent execution strategies for
enacting software robots in dynamic and knowledge-intensive situations, without
the need of manually pre-de ning the behaviours of such robots. Fig.1 shows an
overview of the three-steps approach described in Section 1, for achieving the
aforementioned objective.</p>
      <p>Task-based
logs
RPA Strategy
Interaction
logs
Objective 1: Identify the relevant tasks to be emulated through software robots
by looking at the interaction logs that keep track of the user actions taking place
during a run of the system.</p>
      <p>
        Methodology: Development of a novel method in HCI [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] to analyse
interaction logs for: (i) understanding which user actions have to be captured; (ii)
interpreting their semantics (also) on the basis of their granularity and (iii)
identifying the boundaries of relevant tasks. As a result, the list of user actions
associated to a complete execution of a relevant task during a run of the system
will be recorded into speci c execution traces. Then, all the traces associated to
a relevant task will be clustered in a task-based log.
      </p>
      <p>
        Objective 2: Once identi ed the relevant tasks to be emulated and the user
actions that constitute them (i.e., the task-based logs), the target will be to
automatically generate the owchart diagrams describing the behaviours of
software robots required to successfully executing a systems relevant task.
Methodology: Identify which state-of-the-art algorithms suit better to extract
the base structure of owchart diagrams from a task-based log by resorting
on discovery algorithms from the Process Mining [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] eld, and also on trace
alignment [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] techniques.
      </p>
      <p>Objective 3: Automated synthesis of RPA strategies starting from the owchart
diagrams discovered from the task-based logs.</p>
      <p>
        Methodology: The idea is to leverage automated planning techniques in AI
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] for the synthesis of complex execution strategies, in order to emulate the
enactment not just of single tasks but of interconnected and large work ows as
the composition of many relevant tasks of interest.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Results, impacts and bene ts</title>
      <p>The major results that will be obtained by achieving the objectives of this
research are: the (i) automated identi cation of relevant tasks, the (ii) automated
generation of robots' behaviour and the (iii) automated synthesis of RPA
strategies. Apart from the ability of automatically generating robots' behaviour and
complex strategies of execution for robots starting just from an interaction log,
this research proposal aim at also improving the auditability (interaction logs are
auditable), upgradability ( owchart diagrams describing robots' behaviour will
be always updated to the current state of system's execution, by employing trace
alignment techniques) and the resiliency (the ability of having software robots
that are always upgraded to deal with new behaviours make them very robust
and resilient to any contextual change that may arise during a task execution)
of software robots. Furthermore, scalability will be improved as well. Human
capacity is di cult to scale in situations where demand uctuates, instead
software robots operate at whatever speed is demanded by the work volume. Finally,
we also envision that the proposed research will provide long-term bene ts on
the companies workforce, e.g., improving the customer service in the front o ce
while at the same time reducing the back o ce tasks. Last but not least, the
synthesis of RPA strategies will allow multiple robots to be deployed when demand
exceeds the capacity of a single robot increasing the overall productivity.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          : Process Mining: Data Science in Action. Springer, Heidelberg,
          <volume>2</volume>
          <fpage>edn</fpage>
          . (
          <year>2016</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>662</fpage>
          -49851-4
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bichler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heinzl</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Robotic process automation (</article-title>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Adriansyah</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sidorova</surname>
          </string-name>
          , N.,
          <string-name>
            <surname>van Dongen</surname>
            ,
            <given-names>B.F.</given-names>
          </string-name>
          :
          <article-title>Cost-based tness in conformance checking</article-title>
          .
          <source>2011 Eleventh International Conference on Application of Concurrency to System</source>
          Design pp.
          <volume>57</volume>
          {
          <issue>66</issue>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bisbal</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lawless</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grimson</surname>
          </string-name>
          , J.:
          <article-title>Legacy information systems: Issues and directions</article-title>
          .
          <source>IEEE software 16(5)</source>
          ,
          <volume>103</volume>
          {
          <fpage>111</fpage>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dix</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Human-computer Interaction</article-title>
          .
          <source>In: Encyclopedia of Database Systems</source>
          , pp.
          <volume>1327</volume>
          {
          <fpage>1331</fpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Dumais</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Je</surname>
            <given-names>ries</given-names>
          </string-name>
          , R.,
          <string-name>
            <surname>Russell</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tang</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Teevan</surname>
          </string-name>
          , J.:
          <article-title>Understanding user behavior through log data and analysis</article-title>
          .
          <source>In: Ways of Knowing in HCI</source>
          , pp.
          <volume>349</volume>
          {
          <fpage>372</fpage>
          . Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ghallab</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nau</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Traverso</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <source>Automated Planning: theory and practice</source>
          .
          <source>Elsevier</source>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Hill</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ford</surname>
            ,
            <given-names>W.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Farreras</surname>
            ,
            <given-names>I.G.</given-names>
          </string-name>
          :
          <article-title>Real conversations with arti cial intelligence: A comparison between human{human online conversations and human{chatbot conversations</article-title>
          .
          <source>Computers in Human Behavior</source>
          <volume>49</volume>
          ,
          <issue>245</issue>
          {
          <fpage>250</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Volodymyr</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maggi</surname>
            ,
            <given-names>F.M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.:</surname>
          </string-name>
          <article-title>Multi-perspective process model discovery for robotic process automation</article-title>
          .
          <source>CAiSE Doctoral Consortium</source>
          <volume>2114</volume>
          (
          <issue>9</issue>
          ),
          <volume>37</volume>
          {45 (Jun
          <year>2018</year>
          ), http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>2114</volume>
          /paper5.pdf
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Willcocks</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Service automation : robots and the future of work</article-title>
          . Steve Brookes Publishing, Warwickshire, United
          <string-name>
            <surname>Kingdom</surname>
          </string-name>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>