Data
One log, read once into this container from the mounted project directory. Every module and every job reads this one thing.
| Cases | 1,598 one per purchase_order |
| Events in a case | 8,404 of 14,671 - 57.3% |
| Events in no case | 6,267 counted above, absent from every case figure below |
| Distinct paths | 35 across 1,598 cases |
| Cases on a repeated path | 1,588 99.4% of cases share their path with at least one other |
This log is projected onto purchase_order, and 6,267 of its 14,671 events relate to no purchase_order at all. Those events are in the Events figure at the top of this screen and in nothing below it that counts by case. This log has 7 object types and any of them can be the case notion.
| First event | 01 Apr 2022 09:26 |
| Last event | 31 Oct 2024 20:28 |
| Span | 944 days |
| Events per case | 4 to 9, median 5.0, mean 5.3 |
| Objects | 9,543 |
| Relations | 35,927 |
| goods receipt | 1,941 |
| invoice receipt | 927 |
| material | 2,296 |
| payment | 927 |
| purchase_order | 1,598 |
| purchase_requisition | 927 |
| quotation | 927 |
| Shortest case | 34.7 h |
| Median case | 321.2 h |
| 90th percentile | 532.7 h |
| 95th percentile | 614.3 h |
| Longest case | 1112.3 h |
Percentiles, not a standard deviation: case durations are right-skewed, so a deviation on one says less than it appears to. The unit is chosen from this log's own median.
4 to 9 events per case, counted exactly - event counts are small integers, so nothing is bucketed.
Apr 2022 to Oct 2024, 31 months. Arrivals and completions are counts within each month, so the gap between them is the net change during it. Open cases is the level, and is the backlog. Every month in the range is shown, including the empty ones.
| Activity | Events | Share | Cases | Share | Starts | Ends | First seen | Last seen |
|---|---|---|---|---|---|---|---|---|
| Create Goods Receipt | 4,042 | 27.6% | 1,598 | 100.0% | - | 46.1% | 11 Apr 2022 08:52 | 28 Oct 2024 08:37 |
| Create Invoice Receipt | 1,941 | 13.2% | 0 | - | - | - | 13 Apr 2022 07:49 | 29 Oct 2024 07:55 |
| Perform Two-Way Match | 1,941 | 13.2% | 0 | - | - | - | 13 Apr 2022 07:59 | 29 Oct 2024 08:10 |
| Approve Purchase Order | 1,598 | 10.9% | 1,598 | 100.0% | - | - | 07 Apr 2022 17:28 | 22 Oct 2024 17:36 |
| Create Purchase Order | 1,598 | 10.9% | 1,598 | 100.0% | 100.0% | - | 06 Apr 2022 07:45 | 20 Oct 2024 11:56 |
| Execute Payment | 1,166 | 7.9% | 927 | 58.0% | - | 53.9% | 16 Apr 2022 15:46 | 31 Oct 2024 20:28 |
| Create Request for Quotation | 927 | 6.3% | 0 | - | - | - | 05 Apr 2022 16:09 | 16 Oct 2024 17:45 |
| Create Purchase Requisition | 729 | 5.0% | 0 | - | - | - | 01 Apr 2022 09:26 | 02 Oct 2024 00:19 |
| Approve Purchase Requisition | 607 | 4.1% | 0 | - | - | - | 02 Apr 2022 14:16 | 11 Oct 2024 18:48 |
| Delegate Purchase Requisition Approval | 122 | 0.8% | 0 | - | - | - | 04 Apr 2022 09:44 | 01 Oct 2024 08:25 |
Starts and ends are the share of all 1,598 cases that open or close with that activity. A dash means it never does.
| Attribute | Level | Type | Distinct | Missing | Example | Range |
|---|---|---|---|---|---|---|
| lifecycle | case | VARCHAR | 1 | - | complete | |
| resource | event | VARCHAR | 6 | - | Procurement Department |
A dash under Missing means the attribute has a value on every event. A teal chip on the name is the enrichment layer that computed it.
| Check | Result | What it means |
|---|---|---|
| Events with no timestamp | 0 | A missing timestamp removes the event from every ordering. |
| Events with no activity name | 0 | Unnamed activities cannot be mapped. |
| Exact duplicate events | 739 | Same case, activity and timestamp - usually a double extract. |
| Cases affected by duplicates | 1 | The worst single case carries 1 duplicate event(s). |
| Single-event cases | 0 | A case with one event has no process to analyse. |
| Zero-duration cases | 0 | Start and end at the same instant - often a batch load artefact. |
| Timestamps at midnight exactly | <0.1% | Date-only timestamps make within-day ordering arbitrary. |
| Events sharing a timestamp inside a case | 2 | Their order within the case is arbitrary, so any path through them is. |
| Timestamp granularity | minute | Every timestamp lands exactly on a whole minute, so nothing finer can be ordered. |
| Events out of recorded order | not knowable | There is no recorded source order to compare against - either this log's event ids are not a sequence, or an enrichment layer has added events the source never wrote. |
| Timestamps in the future | 0 | A system default has landed in a real column, and it stretches the span. |
| Timestamps on a sentinel date | 0 | Dates a system writes when it means 'no date': 1970-01-01, 1900-01-01, 1899-12-30. |
| Time span | 944 days | 01 Apr 2022 to 31 Oct 2024 |
| Cases not ending in a common end activity | 0 | Likely still running, or truncated by the extract window. |