In This Article
- The Discovery Gap: What People Say vs What Systems Show
- What Process Mining Actually Does
- How Process Mining Works: Event Logs to Process Maps
- 4 Discovery Patterns for Automation
- Process Mining Tools: Celonis, Microsoft, UiPath
- From Discovery to Automation: The Handoff
- Continuous Mining: Optimizing What You've Already Automated
- Go Deeper
The Discovery Gap: What People Say vs What Systems Show
A shared services team describes their invoice process: "receive invoice, enter data, match to PO, get approval, post." 5 steps, 15 minutes per invoice, straightforward. Process mining tells a different story: the actual process has 47 variants. 25% of invoices cycle through 3-4 rework loops (wrong GL code, missing cost center, amount mismatch requiring re-approval). The "15 minutes" is actually 12 minutes of processing spread across 4 days of waiting in approval queues. And 18% of invoices take a detour through an undocumented email-based exception process that bypasses the workflow system entirely.
Automating the documented 5-step process would capture 53% of the volume. Automating based on the mined reality — all 47 variants, the rework loops, and the email exceptions — captures 90%+ and targets the rework loops that consume more time than the straight-through processing. Automation built on process mining targets reality. Automation built on interviews targets perception.
What Process Mining Actually Does
Process mining analyzes event logs from enterprise systems (ERP, CRM, ticketing, workflow) to reconstruct how business processes actually execute. Every transaction in an ERP generates timestamped events: PO created (10:23 AM), PO approved (2:47 PM next day), goods receipt posted (3 days later), invoice matched (2 days after that). Process mining connects these events into end-to-end process instances and visualizes the actual flow — including all variants, loops, and deviations.
Three Process Mining Capabilities
Process discovery: Automatically generates a process map from event logs — no documentation, no interviews, no assumptions. The map shows every path cases actually follow, the frequency of each path, and the time spent in each step and transition. Discovery reveals process variants that stakeholders didn't know existed.
Conformance checking: Compares the actual process (from event logs) against the designed process (from documentation or compliance requirements). Deviations are flagged: steps skipped, steps executed out of order, unauthorized paths taken. For regulated industries, conformance checking is a compliance tool — proving that processes follow required procedures or identifying where they don't.
Performance analysis: Identifies bottlenecks (where do cases wait?), rework loops (where do cases cycle back?), and throughput variations (why do some cases take 2 days and others take 20?). Performance analysis directs automation investment toward the bottlenecks that matter most — not the steps that are merely manual but the steps that are slow, error-prone, or resource-intensive.
How Process Mining Works: Event Logs to Process Maps
Process mining requires three data elements from each event: Case ID (which process instance — e.g., PO number), Activity (what happened — e.g., "PO Created"), and Timestamp (when — e.g., "2025-03-15 10:23:45"). Additional attributes enrich the analysis: who performed the activity, which system, what values changed. The event log is extracted from the source system's database or audit log — every enterprise system records these events for its own purposes.
| Source System | Event Log Source | Typical Activities |
|---|---|---|
| SAP ERP | CDHDR/CDPOS (change documents), BKPF/BSEG (accounting) | PO created, approved, goods receipt, invoice receipt, payment |
| Salesforce CRM | Activity History, Case History, Opportunity History | Lead created, qualified, opportunity created, quote sent, closed |
| ServiceNow | Task History, Workflow Context | Ticket created, assigned, in progress, resolved, closed |
| Power Automate | Flow run history | Flow triggered, action executed, completed/failed |
4 Discovery Patterns for Automation
High-Volume Straight-Through Paths
The most common process variant — the happy path that 50-70% of cases follow. These are the easiest to automate (rules-based, predictable) and produce the largest volume impact. Automate these first with RPA.
Rework Loops
Cases that cycle back — rejected approvals, returned forms, re-entered data. Rework loops consume 2-5x more resources than straight-through processing per case. AI-assisted data entry (auto-suggest GL codes, validate completeness at entry) prevents rework at the source — higher impact than automating the rework loop itself.
Queue Time Bottlenecks
Steps where cases wait 80% of the time (approval queues, assignment queues, review queues). The processing time is 5 minutes; the waiting time is 3 days. Automating the processing step saves 5 minutes. Automating the routing and escalation eliminates 3 days of wait time — a 100x larger impact on cycle time.
Manual Workarounds
Cases that leave the formal system — email-based approvals, spreadsheet tracking, manual data transfers between systems. These are invisible to traditional analysis but appear in process mining as cases that start in the formal system, disappear, and reappear later. Workarounds indicate: the formal system doesn't handle the case type, the process has an undocumented exception, or the system is too cumbersome for certain scenarios. Automating the workaround (or fixing the root cause) eliminates an entire shadow process.
Process Mining Tools: Celonis, Microsoft, UiPath
| Tool | Best For | Data Connectors | Automation Integration |
|---|---|---|---|
| Celonis | Enterprise-scale, SAP-centric, advanced analytics | SAP, Oracle, Salesforce, ServiceNow, 100+ connectors | Action Engine triggers automations directly |
| Microsoft Process Advisor | Microsoft-stack, integrated with Power Automate | M365, Dynamics, custom via Dataverse | Native Power Automate flow generation |
| UiPath Process Mining | UiPath RPA customers, task-to-process mining | SAP, Oracle, ServiceNow, custom | Direct handoff to UiPath Studio for bot development |
From Discovery to Automation: The Handoff
Process mining produces the automation opportunity map — a prioritized list of automation candidates with: the process variant to automate, the volume and resource consumption, the automation approach (RPA for structured, AI+RPA for unstructured), and the estimated ROI. This map replaces the stakeholder interview as the primary input for automation planning.
The handoff workflow: mining team identifies top 10 automation candidates → scores each against the automation candidate criteria (volume, rules-based, structured, stable) → presents scored candidates to the CoE → CoE selects Wave 1 (top 3-5) → development begins with the process map as the specification (replacing the traditional PDD based on interviews).
Continuous Mining: Optimizing What You've Already Automated
Process mining isn't a one-time discovery exercise — it's a continuous optimization tool. After automation is deployed, continuous mining monitors the automated process: is the automation rate increasing or decreasing? Are new exception patterns emerging? Has the rework loop rate changed? Are there new process variants the automation doesn't handle?
Continuous mining creates a feedback loop: mine → automate → monitor → identify new optimization → automate → monitor. Each cycle increases the automation rate and reduces exception volume. The process gets more automated over time — unlike static RPA that automates at a fixed rate forever. This is the operational discipline that separates programs that plateau at 70% automation from programs that reach 95%.
Process Mining Data Quality Requirements
Process mining quality depends on event log quality. Three data quality requirements must be met: completeness (every relevant activity is captured — if the approval step happens in email rather than the workflow system, the event log has a gap that produces misleading process maps), accuracy (timestamps are correct — systems with batch-updated timestamps instead of real-time event recording produce inaccurate duration measurements), and granularity (individual activities are distinguished — a single "processed" event that covers 5 sub-activities hides the bottleneck within those sub-activities). Before running process mining, audit the event log for these three qualities. If completeness is below 80% (20%+ of activities missing), supplement with additional data sources or address the logging gap before mining. Inaccurate process maps from incomplete data lead to automating the wrong things.
Quick-Start: Mining Your First Process in 2 Weeks
You don't need a 6-month process mining initiative to get value. The quick-start approach: Week 1 — Select one high-volume process (invoice processing, ticket resolution, order fulfillment). Extract the event log from the source system (SQL query against audit tables). Load into the mining tool (Process Advisor or Celonis trial). Generate the process map. Week 2 — Analyze: identify the top 3 bottlenecks and top 3 rework loops. Quantify the time and cost consumed by each. Present findings to the process owner — "your invoices spend 4 days in the approval queue, and 25% cycle through rework for missing GL codes." These findings, produced in 2 weeks, redirect automation investment more effectively than 3 months of stakeholder interviews.
Process Mining + AI: Predictive Process Analytics
Advanced process mining combines historical process data with ML to predict: which in-progress cases will miss their SLA (so intervention can happen before the deadline, not after), which process instances will require rework (so quality checks can be applied proactively), and which path a case is likely to follow (so resources can be allocated in advance). Predictive process analytics transforms mining from a retrospective tool (what happened) into a prospective tool (what will happen) — enabling preemptive action instead of post-hoc analysis.
Task Mining vs Process Mining
Process mining analyzes system-level event logs — activities recorded by enterprise applications. Task mining analyzes desktop-level activity — clicks, keystrokes, application switches recorded on individual workstations. Process mining reveals how workflows flow across systems. Task mining reveals how individual steps are performed within systems. Together, they provide full visibility: process mining identifies which steps are bottlenecks; task mining reveals why those steps take so long (10 clicks across 3 screens instead of 2 clicks in one). UiPath Task Mining and Microsoft Process Advisor both support task-level recording. The combination produces the most accurate automation opportunity map — system-level process optimization plus desktop-level task automation.
The Xylity Approach
We deploy process mining as the first phase of every automation engagement — discovering opportunities from actual system data before building bots. Our automation specialists extract event logs, generate process maps, identify the 4 discovery patterns, and produce the scored automation opportunity map. Mining takes 2-4 weeks. It typically redirects 30-40% of planned automation toward higher-value targets.
Go Deeper
Continue building your understanding with these related resources from our consulting practice.
Discover Automation From Data, Not Interviews
Process mining reveals what actually happens — bottlenecks, rework, workarounds. The discovery method that targets reality, not perception.
Start Your Process Mining Discovery →