A Scoring-Based Approach for Structuredness-Aware Business Process Classification
This paper proposes and evaluates a scoring-based approach that automatically classifies business processes into structuredness categories (structured, semi-structured, loosely structured, and unstructured) by analyzing fine-grained temporal and existential activity relationships within event logs to address the lack of automated support in process mining.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are walking through a giant, bustling city. Some parts of the city are like a subway system: the tracks are laid out, the trains run on a strict schedule, and you know exactly where you will end up if you get on at the right station. Other parts are more like a jazz festival or a chaotic street fair; people wander, conversations start and stop randomly, and the path you take depends entirely on who you bump into and what mood you're in. In the world of business, companies run on "processes"—the step-by-step recipes they use to get things done, like processing an invoice or treating a patient. Some of these recipes are rigid and predictable (like the subway), while others are flexible and messy (like the street fair).
For a long time, computers that analyze these business recipes (a field called "process mining") have been great at mapping out the subway lines. But they've struggled to automatically tell the difference between a rigid subway and a chaotic street fair. They can see the lines, but they can't easily say, "This process is super structured," or "This one is totally loose." This matters because if you try to manage a street fair like a subway, you'll crush the creativity. If you treat a subway like a street fair, you'll cause chaos. The big question is: Can we teach a computer to look at the messy data of a business and instantly know what kind of process it is?
This paper, written by researchers at the Technical University of Munich, says "Yes, we can." They built a new tool that acts like a detective for business processes. Instead of just counting how many different paths a process takes, their tool looks at the tiny relationships between every single step. They found that by giving points (a "score") to specific types of relationships—like "Activity A must happen before Activity B" versus "Activity A and B can happen whenever they want"—they can automatically sort any business process into one of four categories: Structured (the rigid subway), Semi-Structured (a mix of both), Loosely Structured (the flexible street fair), or Unstructured (pure chaos).
Here is how their detective work actually happens, using a simple analogy. Imagine you are trying to figure out the personality of a group of friends just by watching how they hang out.
- The Old Way: You might just count how many times they go to the park together. If they go often, you think they are a tight-knit group. But this misses the nuance.
- The New Way (This Paper): You look at the specific rules of their friendship. Do they always sit in the same order? (That's a "temporal dependency"). If one person shows up, does another have to show up too? (That's an "existential dependency").
The researchers realized that different "personalities" of processes have different "friendship patterns."
- Structured processes are like a military drill. If you see a pattern where "Step A is always followed immediately by Step B," that's a huge clue. It's a rigid rule.
- Loosely structured processes are like a group of friends at a party. "Step A might happen, or it might not," and "Step B could happen before A, or after A, or not at all." This is a pattern of independence.
The team created a computer algorithm that scans a log of business activities (like a diary of everything that happened) and builds a giant scoreboard. It counts how many times it sees "rigid rules" versus "flexible freedom." Then, it applies a special set of weights. Think of it like a video game scoring system:
- If the log is full of "Directly Follows" (A then B, no exceptions), the Structured team gets +3 points.
- If the log is full of "Independence" (A and B have no rules), the Loosely Structured team gets +2.5 points.
- If the log is a mix, the Semi-Structured team gets points.
The computer adds up all the points for each category. The category with the highest score wins. If the top two scores are very close, the computer admits, "I'm not sure, this is a borderline case," which is actually a very honest and useful answer.
To test if their scoreboard worked, the researchers did two things. First, they created fake business processes in a computer simulation. They made some that were perfectly rigid, some that were totally chaotic, and some that were in between. Their algorithm got it right 100% of the time on the clean fake data, and even when they added "noise" (fake mistakes or random glitches to the data), the tool was smart enough to ignore the noise and still find the right answer.
Second, they wanted to see if humans could do it better. They showed eight different process maps to 13 experts (people who study business processes) and asked them to guess the category. The results were interesting:
- The experts were great at spotting the extremes. Everyone agreed on the super-rigid processes and the super-chaotic ones.
- But when it came to the messy middle ground (the semi-structured and loosely structured ones), the humans disagreed. Some thought a process was "semi-structured," others thought it was "loosely structured." It was hard for them to tell the difference.
The computer, however, was consistent. It matched the experts on the easy cases and provided a clear, objective label for the messy middle cases where humans were confused. For example, one real-world process (a game called ChickenHunt) was classified by the computer as "loosely structured." The experts mostly agreed, noting that players had total freedom to choose their moves. Another process, a standard insurance claim, was correctly identified as "semi-structured" because it had rigid parts mixed with flexible choices.
The paper doesn't claim this is a magic wand that solves every problem forever. The authors admit that their tool works best when the data is relatively clean and that the "scoring weights" they used were tuned based on their specific simulations. They also note that if a process is truly "unstructured" (meaning absolutely no rules exist at all), it's a bit of a theoretical edge case, but their tool can still spot it because it sees only independence and no rules.
In the end, this paper suggests that we don't need to guess whether a business process is a subway or a street fair. By looking closely at the tiny rules (or lack of rules) between every single step, a computer can automatically score the process and tell us exactly what kind of beast it is. This helps companies decide how to manage their work: do they need strict rules and checklists, or do they need to give their employees the freedom to be creative? The tool provides a clear, automated answer to that question, turning a confusing mess of data into a simple, understandable label.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.