<!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>
      <journal-title-group>
        <journal-title>S. Pérez);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Slicing Petri nets to reduce their complexity - Abstract</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Carlos Galindo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marisa Llorens</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sergio Pérez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Josep Silva</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>VRAIN, Universitat Politècnica de València</institution>
          ,
          <addr-line>Camí de Vera s/n, E-46022 València</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0001</lpage>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>One of the main problems when transferring Petri net-based technology to the industry is
scalability. Many models and analyses that work in theory are simply not applicable to industrial
real-time systems due to the complexity of these systems.</p>
      <p>In this work, we propose automatic Petri net transformations that allow us to automatically
reduce the size and complexity of a Petri net so that the analyses of interest can be applied to it
while keeping the part of the behavior of the Petri net that we are interested in.</p>
      <p>Our approach is based on Petri net slicing, a technique to extract all those places and transitions
(the slice) that are related to a specified point of interest referred to as slicing criterion. This
slicing criterion is often a set of places in a given Petri net. The part of the Petri net that is
unrelated (e.g., cannot influence) to the slicing criterion is removed; thus, slicing the Petri net
can significantly reduce its size and complexity, making it easier and faster to analyze and
understand.</p>
      <p>We have designed and implemented two diferent slicing algorithms that have been integrated
into an open-source and free tool called pn_slicer. The first algorithm (called maximal
contributing slicing algorithm) extracts from a Petri net all parts (places and transitions) that can
contribute tokens to the slicing criterion. This algorithm is useful for Petri net comprehension
and debugging because the slice always contains all the causes that produced an error in the
slicing criterion (e.g., a place with a token that should not be there or just with more tokens
than it should have).</p>
      <p>The second algorithm (called minimal contributing slicing algorithm) extracts the places and
transitions needed to fire the shortest transition sequence that contributes tokens to some place
in the slicing criterion. This algorithm is useful for component extraction and reuse (the slice is
a subcomponent that can be reused in another net or, e.g., used to understand one specific part
of the net). A variant of this algorithm has also been defined to extract the smallest slice of a
Petri net.</p>
      <p>Acknowledgments
This work has been partially supported by the EU (FEDER) and the Spanish MCI/AEI under
grant PID2019-104735RB-C41, and by the EU’s Horizon 2020 under grant No 952215 (Tailor).</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>