Why your conformance rate always reads 100%
A conformance check that replays a log against a model discovered from that same log cannot find anything. It is a classic process-mining trap, and an easy one to spot.
Read the articleField notes on process mining, task mining and automation. What works, what does not, and why.
A conformance check that replays a log against a model discovered from that same log cannot find anything. It is a classic process-mining trap, and an easy one to spot.
Read the articleCase id, activity, timestamp. Everything else is convenience. What this minimal contract buys you, and what skipping it costs.
Read the articleObserving desktop work without recording what is typed. The distinction is not cosmetic: it decides whether the whole arrangement stands up.
Read the articleA dashboard answers "how many". Process mining answers "in what order, and why so slow". Both read the same databases, and they tell you different things.
Read the articleA read query, a restricted database user and a rolling window. That is the only way to analyse a process without risking any load on the system that runs the company.
Read the articleThe first analysis of a process almost always reveals hundreds of distinct paths. The count is not the problem: what matters is how much volume the first few cover.
Read the articleThe most requested automation, and the worst specified. What has to be settled before a single scenario is written, and what breaks when it is not.
Read the articleNo data engineer, no warehouse, one ERP and two spreadsheets. That is the situation of most industrial SMEs, and it is not an obstacle to a first analysis.
Read the article