Live Operations Correlation key:
report_ref · 98.2%Scheduled report delivery
Live Automated since Dec 2025 — 2.2 h/week reclaimed across everyone who runs it, 71 h to date. 0 h/week of hands-on work is left, and that is the figure quoted everywhere on this page.
Case footprint: median 38m 20s elapsed, 6m 05s of it hands-on, across 1 work session and 0.1 calendar days. 3 of the 6 happy-path waits exceed the 150 s idle-gap threshold, but a gap only ends a work session when it outlasts one (59 min, the fleet's mean). None here do: the case is put down and picked up inside the same sitting, while the person works other cases.
- Cases
- 121
- Activities
- 7
- Variants
- 23
- Median throughput
- 38m 20s
- p95 throughput
- 2.5 h
- Working time / Waiting time
- 6m 05s / 32m 15s
- Rework
- 8%
- Fitness
- 0.94
- Precision
- 0.83
No filters — showing every case
121 of 121 cases (100%)
Directly-follows map
Discovered from the event log. The editable automation design is the last tab.showing 7 of 7 activities · 100% of activity instances covered
Geometry is computed at build time, so nothing reflows when you filter. All 31 directly-follows relations are shown.
Node fill 0–20%20–40%40–60%60–80%80–100% Happy path Loop back Self-loop
Five discrete steps. Edge thickness is a square-root scale on frequency, so the busiest edge is 8 px and the quietest 1 px.
Variant explorer
One row per distinct end-to-end activity sequence, ranked by case count. Row 1 is the happy path and every other row is column-aligned to it, so deviations read as vertical discontinuities.Top 12 variants cover 90.9% of cases.
Select exactly two variants to compare.
| # | Variant | Sequence | Cases | % of cases | Cumulative | Median | p95 | Steps | Δ vs happy path | Conformance | Compare |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | V-01 Happy path | FSBSDODFFD | 48 | 39.7% | 39.7% | 31m 05s | 2.2 h | 5 | — | Conforming | |
| 2 | V-02 | FSBSDOAF×2DFAFFD | 11 | 9.1% | 48.8% | 45m 57s | 5 h | 7 | +2 · 14m 52s | Deviating | |
| 3 | V-03 | FSAF×2BS×3DOBSDFFD | 9 | 7.4% | 56.2% | 56m 29s | 6.8 h | 9 | +4 · 25m 24s | Deviating | |
| 4 | V-04 | FS×3BSDODFFD | 8 | 6.6% | 62.8% | 41m 46s | 4 h | 7 | +2 · 10m 41s | Conforming | |
| 5 | V-05 | FSBSDOAFDFFD×3 | 7 | 5.8% | 68.6% | 52m 42s | 5.9 h | 8 | +3 · 21m 37s | Deviating | |
| 6 | V-06 | RBFSBSDOAFDFRBFD | 6 | 5% | 73.6% | 53m 23s | 6 h | 8 | +3 · 22m 18s | Deviating | |
| 7 | V-07 | FSBSDODFFD | 5 | 4.1% | 77.7% | 24m 43s | 2.6 h | 4 | -1 · -6m 22s | Deviating | |
| 8 | V-08 | FSBSDODFAFFD | 5 | 4.1% | 81.8% | 32m 35s | 2.1 h | 6 | +1 · 1m 30s | Deviating | |
| 9 | V-09 | FSBSDODFAFFD | 4 | 3.3% | 85.1% | 35m 39s | 2.8 h | 5 | — | Deviating | |
| 10 | V-10 | FSBSDOAFDFFD | 3 | 2.5% | 87.6% | 32m 56s | 4.1 h | 6 | +1 · 1m 51s | Deviating | |
| 11 | V-11 | FSBSDOAFDFFD | 3 | 2.5% | 90.1% | 30m 45s | 2.7 h | 5 | — | Deviating | |
| 12 | V-12 | FSBS×3DODFFD | 1 | 0.8% | 90.9% | 37m | 3.7 h | 7 | +2 · 5m 55s | Conforming | |
| — | Other variants (0) · 0% of cases | Activity sequence — | 0 | 0% | 100% | — | — | — | — | — |
12 variants (52.2% of all variants) occur exactly once, together 9.9% of cases.
Variant distribution
Rank on a log scale against cases on a log scale, with cumulative coverage on the right axis.Variant comparison
Two variants on the same alignment columns. Colour says which side; hatching repeats it, so the diff survives greyscale.
A · V-01
Merged activity set
B · V-02
Merged activity set
Every alignment column, coloured by which side uses it.
In both Only in A Only in B In neither
List of changes
| Side by side | A | B | Δ |
|---|
Attributes associated with each branch
These are associations measured on the log, not causes. Every rule prints the number of cases it was measured on.Schedule window schedule_window
116 of 121 cases · 4.4% missing
Compared to the process baseline
Export size (MB) report_size_mb
120 of 121 cases · 0.8% missing
Compared to the process baseline
Department department
119 of 121 cases · 1.8% missing
Compared to the process baseline
Falls in a period end period_end
115 of 121 cases · 5% missing
Compared to the process baseline
Device class device_class
117 of 121 cases · 3.1% missing
Compared to the process baseline
Shift shift
116 of 121 cases · 4.5% missing
Compared to the process baseline
Rule statements
Ranked by lift × support. Each rule is a sentence you can read aloud.When report_size_mb > 29.2 → the case takes “Retry the failed build” in 30.1% of cases (baseline 8.3%, lift 3.63×, n = 8).
When schedule_window = On demand AND period_end = true → the case takes “Alert Ops about the failure” in 92% of cases (baseline 43%, lift 2.14×, n = 12).
When department = Finance AND shift = Afternoon → the case takes “Alert Ops about the failure” in 78.3% of cases (baseline 43%, lift 1.82×, n = 8).
Decision point
Pick an exclusive choice in the map to see its branch shares and the attributes that discriminate between them.
Branch
Branch
Branch
Conformance against the reference model
Reference model v3, 29 Jun 2026Fitness0.94
Precision0.83
Fitness and precision trade off; we report both rather than a single model-quality score.
Conforming cases — 59 (48.8%) Non-conforming — 62 (51.2%)
Deviations by type
A deviation is not necessarily an error — it is behaviour the reference model does not allow.| Breaks conformance | |||||
|---|---|---|---|---|---|
| Activity retry | 42 | 34.7% | 4m 08s | 2.9 h | — |
| Invalid activity | 62 | 51.2% | 78s | 80m 36s | Breaks conformance |
| Skip | 44 | 36.4% | 76s | 55m 44s | Breaks conformance |
| Exclusive-choice violation | 9 | 7.4% | 88s | 13m 12s | Breaks conformance |
| Invalid start/end | 6 | 5% | 0s | 0s | Breaks conformance |
Conforming cases over the window
Conforming cases (%) · 16 Jun – 13 Jul 2026Rework and loops
Self-loops and loop-backs, with loop inflow, outflow and net gain.| Activity | Kind | Self-loops | Cases affected | Mean repeats | Loop in | Loop out | Net gain | Total waiting |
|---|---|---|---|---|---|---|---|---|
| Alert Ops about the failure | Self-loop | 32 | 21 | 2.52× | 32 | 27 | +5 | 20m 45s |
| File the document | Loop back | 0 | 20 | 2× | 20 | 20 | 0 | 5 h |
| Download file | Loop back | 0 | 20 | 2× | 20 | 17 | +3 | 5.3 h |
| Build the report on the server | Loop back | 0 | 11 | 2× | 11 | 8 | +3 | 54m 29s |
| Build the report on the server | Self-loop | 29 | 10 | 3.9× | 29 | 30 | -1 | 62m 08s |
| Schedule fires | Self-loop | 20 | 10 | 3× | 20 | 16 | +4 | 40m 14s |
| File the document | Self-loop | 18 | 9 | 3× | 18 | 16 | +2 | 9m 46s |
| File the document | Loop back | 0 | 8 | 2× | 8 | 7 | +1 | 37m 43s |
Rework cost €152–228 · 10 cases · 8 h Costed at the €25/h loaded rate used everywhere in this dashboard.
Cases
Showing 16 of a 40-case sample drawn from 121 cases, across the 23 variants listed on the Variants tab. The totals above are exact; this table is sampled.| Variant | Roles | Departments | Conformance | |||||
|---|---|---|---|---|---|---|---|---|
| V-01 | 2026-07-10 13:49:45 | 31m 31s | 5 | Operations AnalystSupport Lead | opssupport | 0 | Conforming | |
| V-01 | 2026-07-10 12:43:11 | 41m 48s | 5 | Operations AnalystSupport Lead | ops | 0 | Conforming | |
| V-06 | 2026-07-10 11:42:57 | 10m 41s | 8 | Support LeadOperations Analyst | ops | 1 | Deviating | |
| V-02 | 2026-07-10 11:27:35 | 1.7 h | 7 | Support LeadOperations Analyst | opssupport | 2 | Deviating | |
| V-01 | 2026-07-10 10:16:22 | 22m 16s | 5 | Support Lead | opssupport | 0 | Conforming | |
| V-01 | 2026-07-10 10:13:48 | 32m 27s | 5 | Support LeadOperations Analyst | opssupport | 0 | Conforming | |
| V-01 | 2026-07-10 09:03:19 | 1.7 h | 5 | Support Lead | ops | 0 | Conforming | |
| V-06 | 2026-07-09 13:18:13 | 29m 50s | 8 | Operations AnalystSupport Lead | opssupport | 1 | Deviating | |
| V-01 | 2026-07-09 08:43:55 | 85m 06s | 5 | Operations AnalystSupport Lead | ops | 0 | Conforming | |
| V-07 | 2026-07-08 14:46:28 | 9m 31s | 4 | Operations Analyst | ops | 0 | Deviating | |
| V-01 | 2026-07-07 16:46:58 | 27m 02s | 5 | Support Lead | ops | 0 | Conforming | |
| V-09 | 2026-07-07 09:32:02 | 54m 07s | 5 | Operations AnalystSupport Lead | opssupport | 0 | Deviating | |
| V-01 | 2026-07-06 16:43:31 | 38m 35s | 5 | Support LeadOperations Analyst | opssupport | 0 | Conforming | |
| V-03 | 2026-07-06 14:30:25 | 34m 19s | 9 | Support LeadOperations Analyst | opssupport | 4 | Deviating | |
| V-01 | 2026-07-06 12:11:05 | 68m 20s | 5 | Support LeadOperations Analyst | opssupport | 0 | Conforming | |
| V-14 | 2026-07-06 12:10:55 | 35m 33s | 7 | Support Lead | opssupport | 1 | Deviating |
16 of 40
Live 97% confidence
Automation design
The Map tab is what the event log shows. This is the automation you are designing from it.
ERP clientCRM (web)Outlook
2.2h reclaimed / week across everyone who runs it
You have an unsaved draft of this diagram.
- 1 Schedule fires
- waiting 12m 15s
- 2 Build the report on the server
- waiting 1m 42s
- 3 Deliver to the owners
- waiting 5m 36s
- 4 Download file
- waiting 6m 11s
- 5 File the document
| Field | Value |
|---|---|
report_ref | RPT-2026-75837 |
account | Nordvant Components BV |
amount_eur | €26,230.47 |
region | Iberia |
owner_role | Sales Ops |
contact_phone | +34 ••• ••• 643 · masked at capture (Phone number masked at capture) |
- 1 Schedule fires
- waiting 2m 14s
- 2 Build the report on the server
- waiting 12m 18s
- 3 Deliver to the owners
- waiting 1m 44s
- 4 Download file
- waiting 17m 35s
- 5 File the document
| Field | Value |
|---|---|
report_ref | RPT-2026-20237 |
account | Brightline Media Srl |
amount_eur | €30,299.54 |
region | Nordics |
owner_role | Sales Ops |
contact_phone | +34 ••• ••• 882 · masked at capture (Phone number masked at capture) |
- 1 Retry the failed build
- waiting 61s
- 2 Schedule fires
- waiting 49s
- 3 Build the report on the server
- waiting 35s
- 4 Deliver to the owners
- waiting 87s
- 5 Alert Ops about the failure Invalid activity
- waiting 12s
- 6 Download file
- waiting 1m 58s
- 7 Retry the failed build
- waiting 2m 26s
- 8 File the document
| Field | Value |
|---|---|
report_ref | RPT-2026-87877 |
account | Brightline Media Srl |
amount_eur | €42,303.59 |
region | DACH |
owner_role | Sales Ops |
contact_phone | +34 ••• ••• 363 · masked at capture (Phone number masked at capture) |
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Download file
- 5File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Alert Ops about the failure
- 5Alert Ops about the failure
- 6Alert Ops about the failure
- 7File the document
- 1Schedule fires
- 2Alert Ops about the failure
- 3Alert Ops about the failure
- 4Build the report on the server
- 5Build the report on the server
- 6Build the report on the server
- 7Build the report on the server
- 8Download file
- 9File the document
- 1Schedule fires
- 2Schedule fires
- 3Schedule fires
- 4Build the report on the server
- 5Deliver to the owners
- 6Download file
- 7File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Alert Ops about the failure
- 5Download file
- 6File the document
- 7File the document
- 8File the document
- 1Retry the failed build
- 2Schedule fires
- 3Build the report on the server
- 4Deliver to the owners
- 5Alert Ops about the failure
- 6Download file
- 7Retry the failed build
- 8File the document
- 1Schedule fires
- 2Build the report on the server
- 3Download file
- 4File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Download file
- 5Alert Ops about the failure
- 6File the document
- 1Schedule fires
- 2Deliver to the owners
- 3Download file
- 4Alert Ops about the failure
- 5File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Alert Ops about the failure
- 5Download file
- 6File the document
- 1Schedule fires
- 2Deliver to the owners
- 3Alert Ops about the failure
- 4Download file
- 5File the document
- 1Schedule fires
- 2Build the report on the server
- 3Build the report on the server
- 4Build the report on the server
- 5Deliver to the owners
- 6Download file
- 7File the document
- 1Schedule fires
- 2Build the report on the server
- 3Alert Ops about the failure
- 4Deliver to the owners
- 5Download file
- 6File the document
- 1Schedule fires
- 2Retry the failed build
- 3Build the report on the server
- 4Deliver to the owners
- 5Download file
- 6Retry the failed build
- 7File the document
- 1Schedule fires
- 2Alert Ops about the failure
- 3Build the report on the server
- 4Deliver to the owners
- 5Download file
- 6File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Retry the failed build
- 5Alert Ops about the failure
- 6Download file
- 7File the document
- 1Schedule fires
- 2Build the report on the server
- 3Download file
- 4Retry the failed build
- 5File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Deliver to the owners
- 5Deliver to the owners
- 6Download file
- 7File the document
- 8File the document
- 1Schedule fires
- 2Schedule fires
- 3Build the report on the server
- 4Deliver to the owners
- 5Retry the failed build
- 6Download file
- 7File the document
- 1Schedule fires
- 2Alert Ops about the failure
- 3Alert Ops about the failure
- 4Build the report on the server
- 5Deliver to the owners
- 6File the document
- 1Schedule fires
- 2Build the report on the server
- 3Deliver to the owners
- 4Download file
- 5File the document
- 6File the document
- 7File the document
- 8File the document
- 1Schedule fires
- 2Deliver to the owners
- 3Download file
- 4File the document
- 1Schedule fires
- 2Schedule fires
- 3Schedule fires
- 4Schedule fires
- 5Build the report on the server
- 6Deliver to the owners
- 7File the document