← App Hub
Hoppo Route Engine

How one optimal route
is born from twelve scattered pickups.

And why locking it down is the only way "route deviation" can mean anything at all.

01
Input · Subscriber locations
Twelve homes, one school.
Every subscribing parent gives Hoppo two locations: home and school. That's it. As subscribers join, pins drop on the network map — but they're not yet connected to anything.
1
Pickup address (geo-coded to ±5 m)
2
School entry gate (verified against school database)
3
Required arrival window (e.g. before 7:45 AM)
DPS ROHINI A B C D E F G H I J K L 12 SUBSCRIBERS · 1 DESTINATION · NO ROUTE YET
02
CLUSTER 1 CLUSTER 2 CLUSTER 3 A B H D F I E G J CLUSTERING · GEO-PROXIMITY + ARRIVAL WINDOW
Step · Clustering
Pins group themselves into cab-sized clusters.
Hoppo's engine looks at every subscriber pin and groups them by what one cab can realistically serve — based on geography, the school's required arrival window, and traffic patterns. One cluster becomes one route.
A
Max 4 stops per cab — fits an Innova / Ertiga without turning into a school bus
B
Geo-proximity — pickups within ~2 km of each other prefer the same cluster
C
Arrival constraint — every child must reach school in their stated window
03
Step · Optimization
Inside each cluster, the shortest path wins.
Now Hoppo runs a constrained Travelling Salesman within each cluster — testing pickup orderings against real-time map data — to produce the route that minimizes total trip time without making any single child sit longer than 35 minutes.
→
OSRM & HERE traffic — real distance and time, not straight-line
→
Fairness rule — child first picked up shouldn't sit >35 min total
→
Re-runs daily at 4 AM — accounts for new subs, monsoon, road closures
1 2 3 4 1 2 3 4 1 2 3 4 3 ROUTES · 12 STOPS · OPTIMAL ORDER LOCKED
04
1 2 3 4 LOCKED ±150 m TOLERANCE CORRIDOR BASELINE ESTABLISHED · ALERTS NOW POSSIBLE
Step · Lock the route
This route becomes the truth.
Once optimized, the route is written into the cab's tablet and pushed to every parent's app. The driver sees turn-by-turn directions. Every parent sees the exact stops, the exact times, and a 150-meter tolerance corridor.
✓
Driver can't change it. Any detour requires admin override + reason logged
✓
Tolerance is configurable — 150 m default, schools can tighten to 80 m
✓
Re-lock only on event — new subscriber, school timing change, road closure
05
Step · Live monitoring
The moment the cab leaves the corridor, alerts fire.
Because the route is locked, "deviation" is no longer a vague accusation — it's a math fact. The cab's GPS is 200 m off the route line. The system pushes alerts to admin, school, and every parent on that route within 8 seconds.
!
3 escalation tiers — quiet log → parent alert → admin call-out
!
Auto-resume detection — alert clears when cab returns to corridor
!
Reason capture — driver must record a reason via voice or tap
1 2 3 4 CAB DEVIATION +220 m off route ! LIVE · ROUTE DEVIATION DETECTED · 8 SECONDS AGO
The point

Without a locked route,
"deviation" is just a feeling.

Every safety feature Hoppo sells — route alerts, ETA accuracy, geo-fencing, the parent's live trip view — collapses if the route is fluid. Locking is what makes the whole stack mean something. The engine you just saw is the foundation of it all.

4am
Daily Re-Optimize
±150m
Default Corridor
8s
Alert Latency
35min
Max Child Trip
See live routes in admin →
A venture of Oval Innovations Private Limited  ·  +91 95605 26156  ·  office@ovalinnovations.com