The process you designed.The process that ran.
Upload an export from your ERP or workflow system. ProcessLens reconstructs the path every case actually took — then shows you where the time went, not where the documentation says it should have gone.
The demo is read-only and needs no signup — real data, real analysis.
What you give it
It starts with a file nobody reads.
An export from your ERP, MES or workflow system. Three columns are enough — which case, what happened, and when. Everything after that is derived, not configured.
No process model to draw first. The point is to find out what the process is, and a model you drew would only tell you what you already believed.
case_id,activity,timestampORD-1001,Order Received,2024-03-01T11:00:00ZORD-1001,Credit Check,2024-03-01T11:16:23ZORD-1001,Production Scheduling,2024-03-01T18:47:53ZORD-1001,Manufacturing,2024-03-01T20:38:53ZORD-2001,Quality Check,2024-03-02T18:29:41ZORD-2001,Manufacturing,2024-03-02T20:07:12Z
What it finds
Where the time actually goes.
A bottleneck isn’t the slowest step — it’s the step that takes far longer than every other transition in the same process. That’s a statistical claim, so ProcessLens states the rule instead of implying it: a transition is flagged when it exceeds the third quartile by more than 1.5 times the interquartile range — Tukey’s rule, computed across that process’s own transitions rather than against a threshold someone picked.
What nobody logged
Rework is invisible until you map it.
Nothing in an event log says “this went backwards”. It shows up as a transition returning to a step the case already passed — which only becomes visible once you know what the normal path is.
In this file, three of thirteen cases went back from quality check to manufacturing. Click that edge in the product and you get exactly those three.
- ↺ORD-2001quality check → manufacturing
- ↺ORD-2002quality check → manufacturing
- ↺ORD-2003quality check → manufacturing
The demo is the product, with the data already in it.
Same analysis, same map, same drill-down — running against the file whose numbers you just read. Read-only, no signup, nothing to install.