Loading forensic analysis...
diff --git a/README.md b/README.md index 8322cea..6ecbc9e 100644 --- a/README.md +++ b/README.md @@ -80,6 +80,25 @@ Then ask Claude: *"Run a conformance check against the o2c-simple reference mode Full walkthrough: **[QUICKSTART.md](QUICKSTART.md)** · Five-question demo: **[scripts/demo-walkthrough.md](scripts/demo-walkthrough.md)** · Pattern discovery: **[pattern-discovery/README.md](pattern-discovery/README.md)** +### Full portfolio dashboard — 6 analysis lenses + +Beyond the synthetic demo, the **[portfolio dashboard](demo/portfolio/index.html)** +(live at `/portfolio/`) presents six forensic lenses over **real** datasets. It was +consolidated here from the now-archived `transaction-forensics` repo so everything +lives in one place. + +| Lens | Data source | Scale | Key finding | +|---|---|---|---| +| **Overview** | Architecture + thesis | — | Structured-vs-unstructured gap analysis | +| **CRM Pipeline** | Kaggle CRM Sales Opportunities | 8,800 opportunities | Win rates, velocity, quarter-end compression | +| **BPI Challenge** | BPI Challenge 2019 (4TU.ResearchData) | 251,734 POs · 1.6M events | 57K payment blocks, resource concentration | +| **IDES Compliance** | SAP IDES demo system | 3,132 cases (O2C + P2P) | **7 compliance violations** in SAP's own reference data | +| **Client Cases** | 3 anonymized engagements | 3M+ ERP records | $103K savings, credit-hold overrides, SOD violations | +| **NLP Patterns** | Salesforce/HERB (HuggingFace) | 37,064 documents | 11 communication clusters, approval bottlenecks | + +The NLP pipeline behind the last tab lives in **[`herb-nlp/`](herb-nlp/)** +(TF-IDF + KMeans, optional BERTopic, network + temporal analysis). + ## Proven in the Field Three real consulting engagements motivated this tool. Anonymized, but the figures diff --git a/demo/index.html b/demo/index.html index f4528c1..c43d581 100644 --- a/demo/index.html +++ b/demo/index.html @@ -265,7 +265,8 @@
| Agent | +Win Rate | +Won | +Closed | +Revenue | +
|---|---|---|---|---|
| 1Hayden Neloms | ++ | 107 | +152 | +$272K | +
| 2Maureen Marcano | ++ | 149 | +213 | +$350K | +
| 3Wilburn Farren | ++ | 55 | +79 | +$158K | +
| 4Cecily Lampkin | ++ | 107 | +160 | +$230K | +
| 5Versie Hillebrand | ++ | 176 | +264 | +$188K | +
| 6Moses Frase | ++ | 129 | +195 | +$207K | +
| 7Boris Faz | ++ | 101 | +153 | +$262K | +
| 8James Ascencio | ++ | 135 | +206 | +$414K | +
| 9Corliss Cosme | ++ | 150 | +229 | +$421K | +
| 10Reed Clapper | ++ | 155 | +237 | +$438K | +
Loading forensic analysis...
This dataset comes from a real multinational company (anonymized for BPI Challenge 2019). The process mining community uses it as a benchmark for purchase-to-pay analysis. Our forensic engine processed the full 1.6M event log and surfaced several structural concerns:
+Payment blocks (22.7%) — Nearly 1 in 4 purchase orders hit a payment block requiring human intervention. This signals systematic issues in invoice matching or vendor master data quality. In a healthy P2P process, payment block rates should be under 5%.
+Process variability — With the top 2 variants covering only 32% of cases, the remaining 68% follow hundreds of different paths. This "spaghetti process" pattern makes it difficult to automate, audit, or optimize. Industry benchmarks target 80%+ coverage in the top 5 variants.
+Resource concentration — user_002 processes 10.4% of all events. If this person is unavailable (vacation, resignation), the bottleneck could cascade across the entire P2P process. This is a classic single-point-of-failure that process mining can identify but traditional audits miss.
+SAP IDES is not production data — it's SAP's official demo and training environment. Thousands of consultants learn SAP using this system. Yet our automated conformance checker found 7 compliance violations that exist in the reference data itself.
+This demonstrates two things: (1) Automated process mining catches what manual review misses, even in well-known systems. (2) If reference data contains these patterns, production systems — with real users under real deadline pressure — almost certainly contain more.
+The conformance checking engine uses token-based replay (van der Aalst algorithm) to compare actual event sequences against expected process models. For P2P, the expected model requires: PR → PO → Goods Receipt → Invoice → Payment. Any deviation is flagged, measured, and classified by severity.
+The O2C analysis reveals a different problem: 158 process variants from just 8 activities. This is a "spaghetti process" — technically functional but impossible to audit or optimize at scale. Combined with the 6,578-day max duration (stale orders from the 1990s still open), it paints a picture of a system that works but accumulates technical debt in its process layer.
+