The planning engine behind your product
Building a TMS, a dispatch tool or a field-service app? Dispatchly's engine plans the tours; your software keeps the users, data and workflow. API access is available on request.
- Orders and stops
- Locations, service times, demand, one or more time windows, soft-window penalties, pickup–delivery pairs
- Vehicles
- Depot, capacity, cost, speed profile, attributes (reefer, hazmat, …)
- Drivers and shifts
- Start window, latest end, maximum duty time, break rules
- Travel times
- Distances and time-dependent travel-time profiles per leg
- Tours
- Vehicle and depot per tour, stop sequence
- Schedules
- Arrival, waiting, service and departure per stop; breaks placed
- Figures
- Cost, distance, driving time, load on board after every stop
- Check result
- Verdict of the independent feasibility checker, with any rule violations listed
Supported in one model
Combine them freely: a refrigerated van with a break rule, soft windows and rush-hour travel times is one ordinary request.
- Multiple depots and mixed fleets
- Capacities
- Multiple time windows per stop
- Soft windows with lateness penalties
- Driver start windows and latest end
- Maximum duty time
- Breaks after a set working time
- Time-dependent (rush-hour) travel times
- Pickup and delivery on the same vehicle
- Vehicle and item attributes (skills)
Every plan is checked independently
Optimisers are complex, and complex software has bugs. That is why every Dispatchly plan is replayed by a separate feasibility checker — written independently of the solver — that recomputes times, loads and rules from scratch.
Your software receives the checker's verdict with each result, so a plan that breaks a rule never reaches a driver unnoticed.
Talk to us about your integration
We currently give API access to selected partners. Tell us what you are building, your typical problem size and the rules your tours must respect, and we will get back to you with documentation and test access.