Process and task intelligence.
What your process actually does, not what the diagram says.
Process mining reads the events your business already emits and shows you the process you are really running — its variants, where it waits, where it loops, and where a control was stepped around.
Objects, not a list of steps.
A sales order, its deliveries, its invoices and its payments are different objects whose lives overlap. A flat list of process steps cannot represent that, so the event model is object-centric: each event names the objects it touched, when it occurred and when it was recorded, and which actor caused it.
- Discovery — the process as actually executed, rebuilt from events rather than drawn in a workshop.
- Variant analysis — how many different ways the same thing gets done, and how much of your volume each one carries.
- Conformance against a versioned expected process, so a deviation is measured against something specific rather than a vague norm.
- Cycle and waiting time — and crucially the difference between them, because most of a slow process is waiting rather than working.
- Rework and loop detection — the steps that get done twice.
- Approval and control-bypass evidence — where the control was not applied, with the events that show it.
- Bottleneck and queue analysis — where work piles up, and what it is waiting on.
- Predictive monitoring of cases still in flight, so an intervention is still possible.
- Cross-module root cause — because the delay in your invoicing is very often something that happened in the warehouse.
The paths it is built to follow.
Quote or order to cash
From first enquiry through to the payment matched against the invoice.
Procure to pay
Requisition, order, receipt, match, payment.
Record to report
The close, and everything that has to land before it can run.
Plan, produce and deliver
Works orders through to dispatch and proof.
Returns to refund
The path that most often hides the rework.
Service to resolution
Ticket to cited answer to closure.
Inventory to finance
Movements through to their postings.
Hire to retire
Subject to the restrictions on people data.
Observed practice does not redefine the permitted process.
If everybody skips a step, that is a finding, not a new rule. Process mining updates the evidence; it never updates policy on its own. Two further disciplines matter for honesty: cases still in flight are censored correctly rather than counted as fast, and an event recorded late stays distinguishable from an event that happened late.
Task mining stops at application events.
Discovery uses events the application already emits. Screen recording, keystroke capture, emotion inference and employee productivity ranking are prohibited — not deferred, prohibited — and any future expansion would require employment-law, privacy and worker-representation review before it was even designed.
When the question is about the process rather than the record.
- “Where does our order process actually stall?” — the waiting step, not the busy one.
- “How many ways do we do this?” — the variant count, and what share of volume the top three carry.
- “Is our approval control working?” — the cases where it was bypassed, with the events proving it.
- “Why is this taking longer than last quarter?” — the change point in cycle time and the step that moved.
- “Which of these in-flight cases will breach?” — predictive monitoring while there is still time to act.
Frequently asked questions.
What is object-centric process mining?
Traditional process mining flattens everything to one case identifier, which forces you to pick either the order or the invoice as the thing being followed. Object-centric event data lets one event belong to several objects at once, which is what an order-to-cash process actually looks like.
Does it need me to draw the process first?
No — discovery works without one. Conformance does need a versioned expected process, because a deviation has to be a deviation from something specific.
Will it monitor my staff?
No. It reads events the application emits about business objects. Screen recording, keystroke capture and productivity ranking are prohibited.
Can it change our workflow automatically?
No. Observed practice does not redefine the permitted process. It produces evidence for a person to act on.
See this engine on your own records.
Join the waitlist and ask it something real. Every answer names the engines it used and the records they read.
Join waitlist