Task-Boundary Mode
How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
Cycle Time
Measures wall-clock case duration, decomposes wait vs. active time by PV stage, and identifies handoff bottlenecks.
16,154
Annual Savings (17 users)
950,218
Projected at 1,000 Users (hrs/yr)
4
Findings Surfaced
34h
Median Handoff Wait
2
Surfaced
0
Accepted
0
Remediating
0
Remediated
Findings
Opportunity
Surfaced
High-Latency Handoffs in Follow-up SUSAR Cases
Sequential handoffs between users average 59h wait time (median 34h, max 307h). 41% of the 61 sequential handoffs exceed 3 days. Total of 3,597 hours of wait time across 44 cases in the pilot period.
Opportunity
Surfaced
Intake Session Fragmentation
'View Intake Processing' screen durations (wall-clock time on screen) vary enormously by case type: 'Follow-up Other' averages 3,778s vs 'Other' at 15s (256x ratio). Overall CV is 1725%, indicating extreme fragmentation. 863 intake sessions across 17...
Benchmark
Stage-to-Stage Wait Time
Decomposing case cycle time by PV stage shows vast wall-clock spans (49,392h total) with only 3.6h of focused interaction (dwell). 13,602 stage-mapped events provide an effort proxy where dwell is unavailable. Worst inter-stage transition: 'Intake ->...
Benchmark
Case Type Cycle Time Comparison
Case cycle times (wall-clock) vary significantly by type: 'Initial AE' averages 39h vs 'Unknown' at 0h (6744.4x). Overall: avg 25h (median 1h). Focused interaction (dwell) accounts for 0.0% of wall-clock (avg 0.0h dwell in 25h elapsed per case). Note...