Operating gap
Large hotel pickup lists become difficult to operate when location, guest count, luggage, language, pickup windows and vehicle capacity are planned separately.
Project case study · static MVP
InfraCluster
Pickup clustering
The problem: Large hotel pickup lists become difficult to operate when location, guest count, luggage, language, pickup windows and vehicle capacity are planned separately.
Who it is for: Transport coordinators planning group hotel pickups.
Cluster plan
Scope: UAE pickup planning
My contribution: I translated hotel-pickup constraints into a reviewable clustering method, capacity checks and dispatch-ready output.
- Sample hotel pickup groups
- Vehicle split and editable cost assumptions
- Supervisor review before dispatch handover
Research and product details
Product and operations design
I translated hotel-pickup constraints into a reviewable clustering method, capacity checks and dispatch-ready output.
Workflow response
A clustering workflow that groups hotels into practical operating zones, flags capacity pressure and prepares a clean dispatch handoff to InfraDispatch.
What the prototype proves
The demonstration makes route grouping, capacity pressure and the reason for each proposed split visible to an operations reviewer.
When it applies
Use it for MICE groups, multi-hotel city tours, airport movements and any service where several pickup points must be consolidated into workable routes.
What the demonstration produces.
- Constraint-based clusters
- Vehicle-fit warnings
- Dispatch handover summary
What it does not claim.
Static MVP with illustrative clustering rules. It does not use live traffic, mapping optimisation or production booking data.
Demonstration boundary: Static MVP with illustrative clustering rules. It does not use live traffic, mapping optimisation or production booking data.