Standard class · RJ 1021 · Warszawa → Krakow · Departs 06:00 Friday Apr 17
Price history — last 30 days
Seat availability — last 14 days
Events & observations
This view adopts Wiremind CAYZN’s ‘drill-down as default navigation’ pattern — arguably the UX signature that differentiates CAYZN from competitors like PROS and Revenue Analytics.
Wiremind CAYZN patterns adopted
- 4-level hierarchy: Network → Corridor → Train → Fare Bucket. CAYZN uses Network → Departure → Fare Bucket; we add ‘Corridor’ since Polish rail thinks in corridors (Warszawa-Krakow, etc.).
- Breadcrumb always visible — the analyst never loses context about where they are in the hierarchy.
- No SQL, no report builder — every question answerable by clicking, not querying.
- Zoom-in without losing the zoom-out context — CAYZN’s ‘ghost preview’ pattern: all four levels visible simultaneously in the navigation map.
Why this matters for our project
Our current dashboards present fixed views. Analysts cannot navigate from ‘show me the network’ to ‘show me this specific fare bucket for this specific train on this specific date’ without switching screens. CAYZN’s drill-down pattern gives analysts one unified navigation model across all depths of analysis.
“Made by revenue managers for revenue managers.” — Wiremind on CAYZN. The drill-down pattern emerged because RM analysts need to zoom in and out constantly — never leave a context, just focus deeper.
What we adapt
CAYZN’s Network → Fare Bucket is a 3-level drill-down (they think in ‘departure’ as the mid-level unit). We add Corridor because Polish rail’s commercial connections are structured around city-pair corridors. Adding Corridor as an intermediate level fits how our analysts think about the business: they ask “what’s happening on Warszawa-Krakow?” before asking “what’s happening on RJ 1021?”
What analysts find here
Route: Warszawa → Krakow
Train: RJ 1021
Departure: 06:00 Fri Apr 17
Class: Standard (Economy)
Booking horizon: 7 days out