Glossary
Here you can find explanations for the nomenclature of our tool.
| Term | Explanation |
|---|---|
| Entity Graph | Our core data structure: a knowledge graph that stores all data and relationships inherited from the source system. It serves as the technical backbone for further analysis and configuration. |
| Dimension | A fully configured analytical perspective on a process. Each Dimension defines how data is interpreted, structured, and analyzed based on a specific process view. |
| Case Identifier | A unique identifier used to distinguish between individual process instances. Examples include: Order Number, Employee ID, or Location ID. |
| Causal Hypothesis | An initial, analyst-defined assumption of how a process is expected to flow. It serves as the basis for identifying deviations and validating actual behavior during analysis. |
| Import | The process of loading and transforming source data. This includes both importing data into the Entity Graph and generating a Dimension from that graph. |
| Causal Model | The technical realization of a Causal Hypothesis within a live, imported Dimension. It forms the foundation of all subsequent process modeling layers. |
| Process Model | The highest level of aggregation in the process hierarchy. It represents all events and transitions (Paths) captured during the Import, across all cases. |
| Variant Model | A mid-level aggregation in the Dimension. It groups all events and transitions that follow a specific process variant – i.e., a recurring causal pattern within the data. |
| Case Model | A detailed representation of all events and transitions linked to a single Case Identifier. Each case model reflects the full execution path of one process instance. |
| Case Instance | The most granular representation of a process instance within a Dimension. It captures the actual 1:1 event flow of a case – from start to end, as far as the data allows. |
| Activity Instance | A single occurrence of an activity in a dimension. |
| Path Instance | A single occurrence of a transition between two activities in a dimension. |
| Activity | The abstracted or aggregated form of an activity. In the Builder, it defines import configurations; in a live Dimension, it aggregates data from all related Activity Instances. |
| Path | The abstracted or aggregated form of a transition between two activities. In the Builder, it contains import logic; in a live Dimension, it summarizes data from all Path Instances. |
| Violation | A detected breach in the expected causal logic of a process. See also: Prohibited Path. |
| Allowed Path | A transition between two activities that is expected according to the Causal Hypothesis and the resulting Causal Model. |
| Prohibited Path | A transition between two activities that was not expected based on the Causal Hypothesis, but was observed in the imported data. |
| Context Data | Supplementary data from the source system that is not directly part of the process flow. Examples: Order Volume, Customer Location. Can be used for filters or shown in the Analyzer’s detail view. |