Enterprise DNA

Instead of IBM Process Mining

Stop renting IBM Process Mining. Own your process review system.

We build your version around the work you need to improve, bring your IBM event histories across and run it for you through Omni by Enterprise DNA.

IBM Process Mining SaaS starts at US$4,250 a month, sold annually. That is US$51,000 a year at the published starting rate.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The bill behind the analysis

An enterprise platform bill for a weekly operating question

IBM publishes SaaS pricing from US$4,250 a month and on-premises pricing from US$2,885 a month. Compare the platform you buy with the history analysis and follow-up your team actually uses.

paid

An annual platform commitment

The SaaS starting rate is sold on an annual basis. Ask how much of the platform your weekly review uses.

group

Business and analyst access

The starting SaaS package includes three business users and one analyst user.

storage

Hosted history capacity

The starting SaaS package includes 20 GB of storage. IBM also lists storage add-ons.

route

Process modelling and analysis

IBM lists rework, performance, variants and conformance among its analysis capabilities.

insights

Custom business metrics

IBM supports custom metrics. Your own database lets you define the questions alongside the work you assign.

sync

Connections and broader automation

The platform includes capabilities beyond exported-history review. Agree which connections and operating steps your own version needs.

From history to accountable work

A review that ends with an owner and a next step

Cases

Know which work is still open

Keep observed histories separate from confirmed completion. Imported records start with an unknown status until someone checks.

  • check Case histories with recorded start and end times
  • check Open work beyond your own target
  • check Unknown completion kept out of completed-case averages
  • check A recorded note when someone confirms the case state

Delays

See the gaps without inventing the cause

Review elapsed time between adjacent recorded steps, with missing end times and overlaps kept visible.

  • check Common activity paths and their case counts
  • check Calendar-hour gaps between recorded steps
  • check Repeated activities linked to open improvement work
  • check Completed-case duration alongside each observed path

Checkpoints

Find steps with missing prerequisites

Record your own process checkpoint and its policy reference, then find the histories that need a closer look.

  • check Approval-before-picking and other local checks
  • check Missing or unfinished predecessors flagged for review
  • check Purpose, source accuracy and retention review reminders
  • check Case histories and checkpoint records you can print

Follow-up

Keep the fix beside the evidence

Make the next review about what changed, with a named owner, due date and resolution for each improvement.

  • check Actions attached to a process or a particular case
  • check Overdue improvements in the attention list
  • check Resolution evidence before an action is marked done
  • check Weekly reviews and case handovers drafted from current records

Make it yours

Design your own IBM Process Mining replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from IBM Process Mining. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your IBM Process Mining replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your IBM Process Mining data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Process Mining for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Process Mining for Claude Code

Connected to your own database

Which cases repeat a step, and is anyone following up?

ORDERS

Code
ORD-102
Repeated steps
1
Open actions
1

Ask it anything

Ten questions for your next process review

These included questions combine event history with your improvement work. IBM also supports custom metrics; these are not claims that its platform cannot answer them with configuration.

chat_bubble Which open cases exceed their target without an improvement owner?
chat_bubble Which repeated steps have no open improvement action?
chat_bubble Which closed cases still have an unresolved checkpoint finding?
chat_bubble Which observed paths combine repeated work and completed cases?
chat_bubble Which handovers have gaps longer than the local quiet-work threshold?
chat_bubble Which cases have no activity history at all?
chat_bubble Which imported histories still need an accuracy review?
chat_bubble Which processes have retention reviews due while work remains open?
chat_bubble Which cases have simultaneous starts that make sequence uncertain?
chat_bubble Which overdue actions belong to cases already marked closed?

Switching

How to switch from IBM Process Mining

A move usually involves preparing an event-level export, mapping its fields and rules, checking a test import, then validating the results alongside IBM before you retire it.

  1. 1

    Export event-level history

    Start with the original IBM event history if you can. Otherwise, export event-level records for each case and activity, including start and end times, resource and role where available. IBM's export path is not specified here, so use what your account allows, usually CSV or Excel, and check with IBM Process Mining if you need help. Summary charts are not complete histories.

  2. 2

    Preview and load records

    Map the export's case, activity, start, end, resource and role fields to the new process, then preview a small sample before loading the full history. The import offers a preview that rolls back writes. Check the case count and timestamp offsets, including daylight-saving changes, before proceeding. If you need different fields or rules, map those separately rather than assuming they carry across.

  3. 3

    Reconcile import flags

    Review the preview and the results after loading. Reconcile the case count and check that the source rows and timestamps match what you exported. The importer flags changed or removed rows for explicit reconciliation rather than treating them as a clean refresh. Investigate flagged records against the source before relying on the imported history for process reviews.

  4. 4

    Run both side by side

    Keep IBM Process Mining active for a short period while you review the same process in both systems. Compare case counts, event histories, case status, elapsed gaps, repeated activities and improvement follow-up. Investigate differences against the source records and your process rules. The aim is to confirm that the history and the reviews you need are available before you stop using IBM.

  5. 5

    Retire IBM after sign-off

    Switch off IBM only after the process owner has checked the imported history and confirmed that the replacement covers the work you plan to move. The free version covers exported event-history analysis and improvement follow-up, not every part of IBM Process Mining. Confirm separately whether you still need IBM's simulation, interactive modelling or connections, and agree the scope for any custom views, access controls or automation.

construction

Where the real effort goes

The main work is usually mapping your own fields and process rules, checking timestamps and deciding how much history to bring across. Process models and custom measures need separate mapping, and a long history may need careful reconciliation. If you have Enterprise DNA install and run it, they handle the event-history mapping and bring the agreed records across with you.

Not ready for a call?

Get your IBM Process Mining switch plan by email

We will send you the step-by-step plan for moving your business off IBM Process Mining, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to run it

Do it yourself, make it yours, or have us run it

Open source

Do it yourself

Free MIT code

  1. 1 Clone the repo and run npm install, npm test and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export an event-level IBM history, map the columns and preview the import
  4. 4 Confirm case status and checkpoints, then render your weekly review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your fields, process rules and review documents
  • check Your IBM event histories mapped and reconciled
  • check A web front end where your team needs one
  • check A different technology stack when it suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated inside Omni by Enterprise DNA
  • check Your records brought across and checked with the process owner
  • check Agreed connections to your existing systems
  • check Backups, access controls and ongoing operating support
Book a call with Sam

Questions

Instead of IBM Process Mining, answered

Does this replace every part of IBM Process Mining? expand_more

The free version covers exported event-history analysis and improvement follow-up. We agree the process views, connections, access controls and automation your team needs as part of your custom version. The scope follows the parts of IBM you actually use.

Can we bring our IBM history across in a day? expand_more

The import is one operation once the event-level export is ready and its fields and timestamps are checked. Use the original event history or an event-level export, then reconcile the case count in a test run. Summary charts are not complete histories. Process models and custom measures need separate mapping.

Does a long gap prove we are wasting staff time? expand_more

No. A gap measures elapsed calendar time between recorded steps. It can include nights, weekends or work not captured in the source. Missing ends and overlapping events are shown separately. The process owner checks the cause before deciding what to change.

Do the checks prove compliance? expand_more

No. They flag selected checkpoint and evidence gaps. Privacy reminders cover recorded purpose, source accuracy reviews and retention review dates. Your local policy and legal responsibilities need their own review. A missing record is a reason to investigate, not proof of misconduct.

What do we pay Enterprise DNA for? expand_more

The code is free to install and operate yourself. We charge one setup fee, then a retainer to build your version, bring the records across, connect the agreed systems and look after it. Bring your current bill and the review your team needs to run.

Bring the process that keeps getting stuck

Spend 30 minutes with Sam. Bring your IBM Process Mining bill and one event-history review. We will work through the records, connections and support your own version needs.

Book a call with Sam Get the free version

Process Mining for Claude Code is free and open source, published by Enterprise DNA.

Done paying for IBM Process Mining?

Get your version built