ICPM 2021, Eindhoven
Probabilistic
Trace Alignment
Giacomo Bergami, Free University of Bozen-Bolzano

Fabrizio M. Maggi, Free University of Bozen-Bolzano

Marco Montali, Free University of Bozen-Bolzano
Rafael Peñaloza, University of Milano Bicocca
Execution traces
A process
A process
Conformance
checking
Conformance checking via alignments
Match log trace with the “closest” model trace(s) in terms of “moves with
disagreement”
close
accept
refuse
pay
archive
Order
close, archive
Conformance checking via alignments
Match log trace with the “closest” model trace(s) in terms of “moves with
disagreement”
close
accept
refuse
pay
archive
Order
close, accept, pay, archive close, refuse, archive
close, archive
Conformance checking via alignments
Match log trace with the “closest” model trace(s) in terms of “moves with
disagreement”
close
accept
refuse
pay
archive
Order
close, archive
close accept pay archive
close >> >> archive
close, accept, pay, archive close, refuse, archive
close refuse archive
close >> archive
d=2 d=1
Conformance checking via alignments
Match log trace with the “closest” model trace(s) in terms of “moves with
disagreement”
close
accept
refuse
pay
archive
Order
close, archive
close accept pay archive
close >> >> archive
close, accept, pay, archive close, refuse, archive
close refuse archive
close >> archive
d=2 d=1
Non
conforming
Closest
trace:
close,
refuse,
archive
What if we can “quantify” nondeterminism?
Process model describing stochastic behaviors: likely and unlikely to happen!
close
accept
refuse
pay
archive
Order
10%
90%
What if we can “quantify” nondeterminism?
State of the art
Process model describing stochastic behaviors: likely and unlikely to happen!
close
accept
refuse
pay
archive
Order
10%
90%
Event


log
Measure of “stochastic
language distance”
!
in
fi
nite
What if we can “quantify” nondeterminism?
Our approach: trace by trace…
Process model describing stochastic behaviors: likely and unlikely to happen!
close
accept
refuse
pay
archive
Order
10%
90%
close, archive
What if we can “quantify” nondeterminism?
Our approach: trace by trace…
Process model describing stochastic behaviors: likely and unlikely to happen!
close
accept
refuse
pay
archive
Order
10%
90%
close accept pay archive
close >> >> archive
close, accept, pay, archive close, refuse, archive
close refuse archive
close >> archive
d=2 d=1
P=0.9 P=0.1
close, archive
What if we can “quantify” nondeterminism?
Our approach: trace by trace…
Process model describing stochastic behaviors: likely and unlikely to happen!
close
accept
refuse
pay
archive
Order
10%
90%
close accept pay archive
close >> >> archive
close, accept, pay, archive close, refuse, archive
close refuse archive
close >> archive
d=2 d=1
conforming
?
Closest
trace?
P=0.9 P=0.1
close, archive
Log trace: close, archive
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
Log trace: close, archive
Perfectly
aligned
Terribly
aligned
The only
possible
Impossible
Likely
Unlikely
Model traces
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
Log trace: close, archive
Perfectly
aligned
Terribly
aligned
The only
possible
Impossible
Likely
Unlikely
Model traces
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
Log trace: close, archive
Perfectly
aligned
Terribly
aligned
The only
possible
Impossible
Likely
Unlikely
Model traces
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
close, refuse, archive
close, accept, pay, archive
Log trace: close, archive
Perfectly
aligned
Terribly
aligned
The only
possible
Impossible
Likely
Unlikely
Model traces
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
close, refuse, archive
close, accept, pay, archive
Log trace: close, archive
Perfectly
aligned
Terribly
aligned
The only
possible
Impossible
Likely
Unlikely
Model traces
Probabilistic trace alignment
close
accept
refuse
pay
archive
Order
10%
90%
close, refuse, archive
close, accept, pay, archive
Contributions
• Probabilistic trace alignment as a kNN problem: ranked list
of top “k” model traces combining alignment distance and
probability

• Class of “well-behaved” stochastic Petri nets

• Pipeline to algorithmically attack the problem

• Realization of the pipeline with two ranking strategies: exact
and approximated

• Implementation and experimental evaluation
The model: a special type of…
Main tasks: (1) calculate the probability of a model trace
(2) retrieve all model traces exceeding a minimum probability
Stochastic Petri net with
repeated labels and silent
transitions
Main issue: a visible trace may have in
fi
nitely many
supporting runs (due to silent transitions)
Stochastic Petri net with
repeated labels and silent
transitions
Stochastic Petri net with
repeated labels and silent
transitions
Bounded
Stochastic Petri net with
repeated labels and silent
transitions
Bounded
Work
fl
ow
Well-established notion of what a trace/run is. Runs are
maximal. Adding elements in a run means “looping
more”, which decreases the probability.
Stochastic Petri net with
repeated labels and silent
transitions under “bounded silence”
Bounded
Work
fl
ow
Bounded silence: no loop goes only through silent steps
- at least one visibile transition is needed to indicate
iteration [good for modeling!]
Stochastic Petri net with
repeated labels and silent
transitions under “bounded silence”
Bounded
Work
fl
ow
Bounded silence: between two consecutive visible steps,
there can only be boundedly many invisible ones.
Good properties of the model
1. Execution semantics captured by a finite-state (stochastic)
reachability graph

2. Each trace has finitely many supporting runs

3. Trace probability computable by enumerating those runs and
summing up their probabilities

4. Only finitely many trace exceed a strictly positive probability
threshold

5. For a log trace, there is a maximal length over model traces
after which alignment distance and probability both decrease
Algorithmic pipeline
Algorithmic pipeline
Algorithmic pipeline
Algorithmic pipeline
Algorithmic pipeline
Algorithmic pipeline
EXACT ALIGNMENT
For each log trace…

1. Invoke an exact aligner on all extracted model traces

2. Rank according to the probability-alignment distance combination
Algorithmic pipeline
APPROXIMATE ALIGNMENT via embeddings
1. Pre-embed all extracted model traces

2. For each log trace… 

A. Embed the log trace

B. Rank by embedding distance
Algorithmic pipeline
APPROXIMATE ALIGNMENT via embeddings
1. Pre-embed all extracted model traces

2. For each log trace… 

A. Embed the log trace

B. Rank by embedding distance
Algorithmic pipeline
APPROXIMATE ALIGNMENT via embeddings
1. Pre-embed all extracted model traces

2. For each log trace… 

A. Embed the log trace

B. Rank by embedding distance
Algorithmic pipeline
APPROXIMATE ALIGNMENT via embeddings
1. Pre-embed all extracted model traces

2. For each log trace… 

A. Embed the log trace

B. Rank by embedding distance
Experiments (sepsis data set)
E
ffi
ciency and suitability of approximation
Results:

• Many model traces —> exact approach struggles

• Long model traces —> approximation decreases in quality

• Current approximation based on bi-grams (embedding in pairs)

• N-grams improve approximation on long traces, but require more
prerocessing time for building the embedding space
Conclusions
• Stochastic conformance checking at the single trace level

• Suitable underlying formal model

• Algorithmic pipeline: approximated alignments based on well-
established techniques from databases and information retrieval

What’s next?
• Explore more the formal guarantees of the model

• Explore more about models (cf. declarative)

• Explore more the approximation spectrum

More Related Content

PDF
From Case-Isolated to Object-Centric Processes - A Tale of two Models
PDF
Reasoning on Labelled Petri Nets and Their Dynamics in a Stochastic Setting
PDF
Constraints for Process Framing in Augmented BPM
PDF
PDF
Process Reasoning and Mining with Uncertainty
PDF
From Case-Isolated to Object-Centric Processes
PDF
Modeling and Reasoning over Declarative Data-Aware Processes
From Case-Isolated to Object-Centric Processes - A Tale of two Models
Reasoning on Labelled Petri Nets and Their Dynamics in a Stochastic Setting
Constraints for Process Framing in Augmented BPM
Process Reasoning and Mining with Uncertainty
From Case-Isolated to Object-Centric Processes
Modeling and Reasoning over Declarative Data-Aware Processes

More from Faculty of Computer Science - Free University of Bozen-Bolzano (20)

PDF
Soundness of Data-Aware Processes with Arithmetic Conditions
PDF
Strategy Synthesis for Data-Aware Dynamic Systems with Multiple Actors
PDF
Extending Temporal Business Constraints with Uncertainty
PDF
Extending Temporal Business Constraints with Uncertainty
PDF
Modeling and Reasoning over Declarative Data-Aware Processes with Object-Cent...
PDF
Enriching Data Models with Behavioral Constraints
PDF
Representing and querying norm states using temporal ontology-based data access
PDF
Compliance monitoring of multi-perspective declarative process models
PDF
Processes and organizations - a look behind the paper wall
PDF
Formal modeling and SMT-based parameterized verification of Data-Aware BPMN
PDF
Modeling and reasoning over declarative data-aware processes with object-cent...
PDF
10 Years Playing with Declare and Temporal Logics on Finite Traces
PDF
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 1: ...
PDF
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 3: ...
PDF
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 2: ...
Soundness of Data-Aware Processes with Arithmetic Conditions
Strategy Synthesis for Data-Aware Dynamic Systems with Multiple Actors
Extending Temporal Business Constraints with Uncertainty
Extending Temporal Business Constraints with Uncertainty
Modeling and Reasoning over Declarative Data-Aware Processes with Object-Cent...
Enriching Data Models with Behavioral Constraints
Representing and querying norm states using temporal ontology-based data access
Compliance monitoring of multi-perspective declarative process models
Processes and organizations - a look behind the paper wall
Formal modeling and SMT-based parameterized verification of Data-Aware BPMN
Modeling and reasoning over declarative data-aware processes with object-cent...
10 Years Playing with Declare and Temporal Logics on Finite Traces
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 1: ...
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 3: ...
BPM2017 - Integrated Modeling and Verification of Processes and Data Part 2: ...
Ad

Probabilistic Trace Alignment

  • 1. ICPM 2021, Eindhoven Probabilistic Trace Alignment Giacomo Bergami, Free University of Bozen-Bolzano Fabrizio M. Maggi, Free University of Bozen-Bolzano Marco Montali, Free University of Bozen-Bolzano Rafael Peñaloza, University of Milano Bicocca
  • 6. Conformance checking via alignments Match log trace with the “closest” model trace(s) in terms of “moves with disagreement” close accept refuse pay archive Order close, archive
  • 7. Conformance checking via alignments Match log trace with the “closest” model trace(s) in terms of “moves with disagreement” close accept refuse pay archive Order close, accept, pay, archive close, refuse, archive close, archive
  • 8. Conformance checking via alignments Match log trace with the “closest” model trace(s) in terms of “moves with disagreement” close accept refuse pay archive Order close, archive close accept pay archive close >> >> archive close, accept, pay, archive close, refuse, archive close refuse archive close >> archive d=2 d=1
  • 9. Conformance checking via alignments Match log trace with the “closest” model trace(s) in terms of “moves with disagreement” close accept refuse pay archive Order close, archive close accept pay archive close >> >> archive close, accept, pay, archive close, refuse, archive close refuse archive close >> archive d=2 d=1 Non conforming Closest trace: close, refuse, archive
  • 10. What if we can “quantify” nondeterminism? Process model describing stochastic behaviors: likely and unlikely to happen! close accept refuse pay archive Order 10% 90%
  • 11. What if we can “quantify” nondeterminism? State of the art Process model describing stochastic behaviors: likely and unlikely to happen! close accept refuse pay archive Order 10% 90% Event log Measure of “stochastic language distance” ! in fi nite
  • 12. What if we can “quantify” nondeterminism? Our approach: trace by trace… Process model describing stochastic behaviors: likely and unlikely to happen! close accept refuse pay archive Order 10% 90% close, archive
  • 13. What if we can “quantify” nondeterminism? Our approach: trace by trace… Process model describing stochastic behaviors: likely and unlikely to happen! close accept refuse pay archive Order 10% 90% close accept pay archive close >> >> archive close, accept, pay, archive close, refuse, archive close refuse archive close >> archive d=2 d=1 P=0.9 P=0.1 close, archive
  • 14. What if we can “quantify” nondeterminism? Our approach: trace by trace… Process model describing stochastic behaviors: likely and unlikely to happen! close accept refuse pay archive Order 10% 90% close accept pay archive close >> >> archive close, accept, pay, archive close, refuse, archive close refuse archive close >> archive d=2 d=1 conforming ? Closest trace? P=0.9 P=0.1 close, archive
  • 15. Log trace: close, archive Probabilistic trace alignment close accept refuse pay archive Order 10% 90%
  • 16. Log trace: close, archive Perfectly aligned Terribly aligned The only possible Impossible Likely Unlikely Model traces Probabilistic trace alignment close accept refuse pay archive Order 10% 90%
  • 17. Log trace: close, archive Perfectly aligned Terribly aligned The only possible Impossible Likely Unlikely Model traces Probabilistic trace alignment close accept refuse pay archive Order 10% 90%
  • 18. Log trace: close, archive Perfectly aligned Terribly aligned The only possible Impossible Likely Unlikely Model traces Probabilistic trace alignment close accept refuse pay archive Order 10% 90% close, refuse, archive close, accept, pay, archive
  • 19. Log trace: close, archive Perfectly aligned Terribly aligned The only possible Impossible Likely Unlikely Model traces Probabilistic trace alignment close accept refuse pay archive Order 10% 90% close, refuse, archive close, accept, pay, archive
  • 20. Log trace: close, archive Perfectly aligned Terribly aligned The only possible Impossible Likely Unlikely Model traces Probabilistic trace alignment close accept refuse pay archive Order 10% 90% close, refuse, archive close, accept, pay, archive
  • 21. Contributions • Probabilistic trace alignment as a kNN problem: ranked list of top “k” model traces combining alignment distance and probability • Class of “well-behaved” stochastic Petri nets • Pipeline to algorithmically attack the problem • Realization of the pipeline with two ranking strategies: exact and approximated • Implementation and experimental evaluation
  • 22. The model: a special type of… Main tasks: (1) calculate the probability of a model trace (2) retrieve all model traces exceeding a minimum probability Stochastic Petri net with repeated labels and silent transitions Main issue: a visible trace may have in fi nitely many supporting runs (due to silent transitions)
  • 23. Stochastic Petri net with repeated labels and silent transitions
  • 24. Stochastic Petri net with repeated labels and silent transitions Bounded
  • 25. Stochastic Petri net with repeated labels and silent transitions Bounded Work fl ow Well-established notion of what a trace/run is. Runs are maximal. Adding elements in a run means “looping more”, which decreases the probability.
  • 26. Stochastic Petri net with repeated labels and silent transitions under “bounded silence” Bounded Work fl ow Bounded silence: no loop goes only through silent steps - at least one visibile transition is needed to indicate iteration [good for modeling!]
  • 27. Stochastic Petri net with repeated labels and silent transitions under “bounded silence” Bounded Work fl ow Bounded silence: between two consecutive visible steps, there can only be boundedly many invisible ones.
  • 28. Good properties of the model 1. Execution semantics captured by a finite-state (stochastic) reachability graph 2. Each trace has finitely many supporting runs 3. Trace probability computable by enumerating those runs and summing up their probabilities 4. Only finitely many trace exceed a strictly positive probability threshold 5. For a log trace, there is a maximal length over model traces after which alignment distance and probability both decrease
  • 34. Algorithmic pipeline EXACT ALIGNMENT For each log trace… 1. Invoke an exact aligner on all extracted model traces 2. Rank according to the probability-alignment distance combination
  • 35. Algorithmic pipeline APPROXIMATE ALIGNMENT via embeddings 1. Pre-embed all extracted model traces 2. For each log trace… A. Embed the log trace B. Rank by embedding distance
  • 36. Algorithmic pipeline APPROXIMATE ALIGNMENT via embeddings 1. Pre-embed all extracted model traces 2. For each log trace… A. Embed the log trace B. Rank by embedding distance
  • 37. Algorithmic pipeline APPROXIMATE ALIGNMENT via embeddings 1. Pre-embed all extracted model traces 2. For each log trace… A. Embed the log trace B. Rank by embedding distance
  • 38. Algorithmic pipeline APPROXIMATE ALIGNMENT via embeddings 1. Pre-embed all extracted model traces 2. For each log trace… A. Embed the log trace B. Rank by embedding distance
  • 39. Experiments (sepsis data set) E ffi ciency and suitability of approximation Results: • Many model traces —> exact approach struggles • Long model traces —> approximation decreases in quality • Current approximation based on bi-grams (embedding in pairs) • N-grams improve approximation on long traces, but require more prerocessing time for building the embedding space
  • 40. Conclusions • Stochastic conformance checking at the single trace level • Suitable underlying formal model • Algorithmic pipeline: approximated alignments based on well- established techniques from databases and information retrieval What’s next? • Explore more the formal guarantees of the model • Explore more about models (cf. declarative) • Explore more the approximation spectrum