Good afternoon.
What do you want to know about this process?
Which cases break a rule?
Where does the time go?
How many different paths are there?
What is this data made of?
STEP 1
Digital Onboarding
loan_origination.parquet - loaded once into this container
LOG
28 Apr 2025 to 11 May 2026
281,743
events
10,000
cases
40
activities
0
case attrs
Modules
Data
One log, its objects and its quality baseline
281,743 events
Process Maps
The whole log as one map - filter it, drill into it
40 activities
Variants
Every distinct path, most common first
261 variants
Conformance
Say a rule in one sentence, see real breaches
2,698 open breaches
Performance
Where the time goes, ranked, cause named
median 346 h
Automations
What should we automate first, and what is it worth?
NOT BUILT
Task Mining
What actually happens on the desktop, between the system events?
NOT BUILT
Simulation
Change the process on paper, not in production.
NOT BUILT
Predictions
Which running cases will miss the deadline - flagged days before it happens.
NOT BUILT
AI Jobs
Anything the modules have no button for
0 default jobs
Alerts
Anything worth finding once is worth watching forever.
NOT BUILT
Scheduled reports
Reports that arrive on a pulse - whether or not anything is wrong.
NOT BUILT
Library
Everything this project has produced, as it sits on disk
0 saved
What this sample is
This entire page - the rail, the menus, every module and the AI Jobs runner - is served by
one Python process inside one Docker container, reading one event log from the mounted
project directory. There is no API tier and no second container.