Interpreted Groups — Knowledge Report

Exported 8/13/2026, 1:11:25 PM · BPI Challenge 2013 — IT incident management (Volvo IT / VINST)
Interpreted groups accumulate here — from obvious/outlier groups (step 1), homogeneous clusters, and manual selections (step 5). Each entry's traces are excluded from "remaining" everywhere in the app once added. Each card now also carries a small fingerprint panel (recent addition) — every case attribute the group has enough data to check, laid out together, with the ones that actually diverge from the whole dataset outlined — so the record captures not just what the group is, but a first-pass account of why. This tab is also where the next subset to investigate gets picked: either the whole "Remaining" pool, or an existing group reopened because it turned out not homogeneous enough — either way, the choice loops back to 2. Encoding.
Groups — 2D arrangement
hover a group for details · click to jump to its card on the right
How this is arranged: each interpreted group is reduced to a simple feature vector (the proportion of its traces' events belonging to each activity type), then projected to 2D via PCA (principal component analysis) — groups with similar behavioral profiles land near each other, dissimilar ones land far apart. Pie size ∝ √(trace count); slices show the outcome mix. This is a rough visual arrangement for orientation, not a precise similarity measure.
All interpreted groups — click a column header to sort; hover a row or a pie above to cross-highlight
# ▲sizeoutcomesdominant %SO
01,74998%–0.90
1616100%3.2×1.00
247392%2.9×0.69
325190%3.0×0.66
4135100%3.0×1.00
519076%2.4×0.31
628378%2.8×0.35
724875%2.6×0.31
816076%2.7×0.37
Remaining / unexplained
3,448 of 7,553 traces (45.7%) not yet interpreted.
reached_line_2: 1,790 (52%)line_1_only: 1,309 (38%)reached_line_3: 349 (10%)
Interpreted groups
9 groups interpreted — 4,105 of 7,553 traces (54.3% of the full dataset) explained so far; 3,448 traces (45.7%) remain, still unexplained.

Obvious group: Accepted_In_Progress → Accepted_In_Progress → Completed_In_Call (S – · O 0.90)

1,749 traces (23.2% of full dataset) · outcome purity 98% (line_1_only) · source: obvious-group (step 1) · added 1:09:11 PM
Selected via: obvious group Accepted_In_Progress → Accepted_In_Progress → Completed_In_Call
line_1_only: 1,720 (98%)reached_line_2: 29 (2%)
highest support line reached
1 98% (+38pp)
ever in "Wait User" status
true 0%
starting support line
1 98% (+10pp)
distinct teams involved
1 (0.6×)
trace length (N actions)
3 (0.3×)
team handoffs
0 (0.0×)

Topic T1-dominant (K=14, step 4) (S 3.2× · O 1.00)

616 traces (8.2% of full dataset) · outcome purity 100% (line_1_only) · source: topic (step 4) · added 1:09:48 PM
Selected via: topic T1 (K=14) — top terms: n_distinct_groups:low (1.915), n_group_changes:low (1.915), ever_wait_user:false (1.237), Accepted_In_Progress->Completed_Resolved (1.105)
line_1_only: 616 (100%)
highest support line reached
1 100% (+40pp)
ever in "Wait User" status
true 0%
starting support line
1 100% (+11pp)
distinct teams involved
1 (0.6×)
trace length (N actions)
4 (0.5×)
team handoffs
0 (0.0×)

Topic T6-dominant (K=14, step 4) (S 2.9× · O 0.69)

473 traces (6.3% of full dataset) · outcome purity 92% (reached_line_2) · source: topic (step 4) · added 1:09:48 PM
Selected via: topic T6 (K=14) — top terms: first_line:2 (1.723), ever_wait_user:false (0.135), Accepted_In_Progress->Completed_Resolved (0.116), Completed_Resolved (0.1)
reached_line_2: 433 (92%)reached_line_3: 40 (8%)
starting support line
2 100% (+91pp)
highest support line reached
1 0%
ever in "Wait User" status
true 15%
distinct teams involved
1 (0.7×)
trace length (N actions)
5 (0.6×)
team handoffs
0 (0.3×)

Topic T9-dominant (K=14, step 4) (S 3.0× · O 0.66)

251 traces (3.3% of full dataset) · outcome purity 90% (line_1_only) · source: topic (step 4) · added 1:09:49 PM
Selected via: topic T9 (K=14) — top terms: Completed_In_Call (1.113), Accepted_In_Progress->Completed_In_Call (1.068), Completed_In_Call->Accepted_In_Progress (0.535), Accepted_In_Progress (0.294)
line_1_only: 227 (90%)reached_line_2: 24 (10%)
highest support line reached
1 90% (+30pp)
starting support line
1 100% (+11pp)
ever in "Wait User" status
false 61%
distinct teams involved
1 (0.8×)
team handoffs
0 (0.4×)
trace length (N actions)
7 (0.8×)

Topic T13-dominant (K=14, step 4) (S 3.0× · O 1.00)

135 traces (1.8% of full dataset) · outcome purity 100% (reached_line_3) · source: topic (step 4) · added 1:09:50 PM
Selected via: topic T13 (K=14) — top terms: first_line:3 (1.309), Accepted_In_Progress (0.079), Queued_Awaiting_Assignment (0.058), Queued_Awaiting_Assignment->Accepted_In_Progress (0.058)
reached_line_3: 135 (100%)
starting support line
3 100% (+98pp)
highest support line reached
3 100% (+93pp)
ever in "Wait User" status
false 61%
trace length (N actions)
7 (0.8×)
team handoffs
1 (0.8×)
max gap
10d (1.2×)

Homogeneous cluster: T9-dominant, 76% line_1_only (S 2.4× · O 0.31)

190 traces (2.5% of full dataset) · outcome purity 76% (line_1_only) · source: homogeneous cluster (step 5) · added 1:11:19 PM
Selected via: k-means cluster 0 — topic-weight profile: T9=0.24, T3=0.038, T0=0.035
line_1_only: 144 (76%)reached_line_2: 41 (22%)reached_line_3: 5 (3%)
highest support line reached
1 76% (+16pp)
starting support line
1 95% (+7pp)
duration
18d (1.5×)
max gap
12d (1.4×)
trace length (N actions)
10 (1.1×)
team handoffs
1 (0.9×)

Homogeneous cluster: T1-dominant, 78% line_1_only (S 2.8× · O 0.35)

283 traces (3.7% of full dataset) · outcome purity 78% (line_1_only) · source: homogeneous cluster (step 5) · added 1:11:21 PM
Selected via: k-means cluster 14 — topic-weight profile: T1=0.257, T0=0.037, T3=0.02
line_1_only: 222 (78%)reached_line_2: 53 (19%)reached_line_3: 8 (3%)
ever in "Wait User" status
false 0%
highest support line reached
1 78% (+18pp)
starting support line
1 99% (+10pp)
team handoffs
0 (0.4×)
trace length (N actions)
6 (0.7×)
distinct teams involved
1 (0.8×)

Homogeneous cluster: T5-dominant, 75% line_1_only (S 2.6× · O 0.31)

248 traces (3.3% of full dataset) · outcome purity 75% (line_1_only) · source: homogeneous cluster (step 5) · added 1:11:21 PM
Selected via: k-means cluster 19 — topic-weight profile: T5=0.253, T3=0.052, T0=0.029
line_1_only: 186 (75%)reached_line_2: 56 (23%)reached_line_3: 6 (2%)
ever in "Wait User" status
false 0%
highest support line reached
1 75% (+15pp)
starting support line
1 96% (+7pp)
trace length (N actions)
11 (1.3×)
team handoffs
1 (0.5×)
distinct teams involved
2 (0.9×)

Homogeneous cluster: T4-dominant, 76% line_1_only (S 2.7× · O 0.37)

160 traces (2.1% of full dataset) · outcome purity 76% (line_1_only) · source: homogeneous cluster (step 5) · added 1:11:22 PM
Selected via: k-means cluster 23 — topic-weight profile: T4=0.221, T3=0.094, T8=0.022
line_1_only: 121 (76%)reached_line_2: 38 (24%)reached_line_3: 1 (1%)
ever in "Wait User" status
true 3%
highest support line reached
1 76% (+15pp)
distinct teams involved
1 (0.7×)
team handoffs
0 (0.2×)
trace length (N actions)
7 (0.8×)
starting support line
3 0%