Recommendation types are separated: sequence improvement is active,
road-choice scoring uses our cascade plus available live signals
(bus AVL, weather, closures, zone congestion). Cascade-validated.
Compared against: Routific (third-party planner)
Point-by-point local resequence
Each card compares the stop's old two-leg context with its suggested
new context. The optimizer keeps moves only when the full cascade
re-run confirms an improvement.
Customer time-window suggestions
These stops are still projected late after optimization. The TW is
binding — the optimizer can't make the close on its own. Operator
action required: extend the customer's window, reschedule earlier in
the day, or split the delivery to another route.
Routific plan vs our smart-cascade ETA
hover a row to highlight the leg · click to zoom · times in EDT (local)
#
id
Routific arr
Our P50
Our P95
pkg
bldg
svc
TW (EDT)
click "Load CSV" in the right panel to load the Routific result
Routific stop
⚠N% = our cascade's prob_late
our P50/P95 includes drive + service + curb + building
Routific
What we see
Axel
What we recommend
Alerts
All clear
Routific · what we see
Axel · what we recommend
Your Plan vs Axel Forecast
Calibrating forecast…
Forecasted Missed Windows
—of — stops
—
Driver Overtime
—min over plan
—
———
Stops Off Plan
—of — stops
—
—missed
—behind plan
—on track
—has slack
All —
At risk —
Behind plan —
Has slack —
Stop InfoRoutific · ExpectedService Time
Route complete — driver finished day
0
Customer Window
Routific
Expected
⚑
Your Optimized Plan
Loading optimized plan…
Optimize for
Forecasted Missed Windows
—of — stops—
Driver End of Day
—min vs Routific—
Routific —Axel —
All—Moved—Window met—
Stop InfoAxel ArrivalService Time
Action required
No active disruptions
System monitoring traffic & incident feeds
📡
All clear — no disruptions detected
Watching MTA bus reroute clusters, NYC 511 incidents, and Google traffic feeds. Action will appear here when something demands attention.