What is X tools?
X tools is the optimisation layer for executing last-mile deliveries. There are three main problems in high-density last-mile delivery problems that are optimised by X tools. Fundamentally, it is combinatorial optimisation and integer programming solved using a constraint programming solver designed to run in the on-board computer of an autonomous delivery asset.
How to use X tools?
X tools is a simple API tool with micro services architecture that will find optimised next steps to be executed by fleets of autonomous delivery vehicles. We release X tools because it can already generate value for current last-mile delivery modes. You can request for API access, submit an REST API call with necessary info, X tools will compute and send you back the results.
BatchX
Batches is an API tool to batch orders efficiently from a single pickup point. It will help in influencing the order picking sequence. The return values from the optimiser can be used in assigning pickers at the warehouse and pack deliveries for transport
RouteX
RouteX is an API tool to efficiently find the next pickup location. This does not provide a route but points the delivery assets independent of their origin location to efficiently choose the next fastest pickup location.
ScheduleX
ScheduleX is an API tool to create efficient trips with large delivery windows and limitations on delivery asset capacity. A delivery asset can have different capacities and Schedulex will generate trips for all different assets.
How to get access?
Use the contact form to get in touch with us. It is a free 30 min call from the X tools team to help you set up the API. We will provide you with API access information and activate your account. We will also provide you with a rundown on how to use X tools.
Currently, only BatchX is openly available for API access.
BatchX
Use case
In the case of a dark store, there is a certain service area for every dark store and a limited amount of riders. This API will provide you with an efficient plan to batch orders from this dark store.
This will reduce the number of trips made by riders by accumulating more than 1 order to the same trip. Here the pickup point is always the same. Route sequences are generated in batches.
How BatchX works?
The top 10 orders (most recent) for that dark store are used as the number of total orders for batching.
The limit is set at the maximum round trip time of a single order in the pool of 10 and provides sequence candidates in batches for these orders.
It is possible to pool more than 10 orders, but for a 10-minute delivery window guarantee, a longer batch sequence or an earlier delivery for an order that is made recently will create unfair service in last-mile delivery.
Most of all, the computation time will increase significantly with a larger pool size.
If you want to execute with a larger pool size, please contact the X tools team to make custom deployments.
How to integrate BatchX?
The X tools team will provide you with the access details during our first call.
REST API is used as the basis for communication.
API access information is used to authenticate the client and the JWT token can be used for sending further requests.
A POST request is used to send order information for a specific dark store. Address as string can be sent, time of order creation and which dark store the order belongs to. We use google maps geocoding API to find the lat, long information from the address string. If location is already available as {lat: float, lng: float}, you can send this information.
A real-time messaging trigger is used to notify events after a batch sequence is created.
Darkstore is created and this will be used along with the orders for batch computation.
RouteX
Use case
Ideal for multiple riders/robots on the field and want to route to the next best asset to pickup
can be combined with BatchX to better accommodate multiple orders in a single pickup.
Routex is an API tool to efficiently route each delivery rider towards the next pickup location. This moves away from the hub and spoke model of a central pickup point. The typical use case would be to route delivery riders efficiently to the next fastest location and make the riders independent of their origin location.
API access coming soon.
ScheduleX
Use case
If you receive orders to be delivered in a future time window. This API will include all the orders and create a trip sequence respecting the time windows of each of the customers. This API will compute to provide you with the number of delivery vehicles that will be required to complete all the trips that are generated as a sequence.
ScheduleX is an API tool to create efficient trips with large delivery windows and limitations on delivery asset capacity. A delivery asset can have different capacities and Schedulex will generate trips for all different assets.
Batchx
batch orders at single pickup- This feature is included
- This feature is included
- This feature is included
- This feature is included
- This feature is not included
- This feature is not included
Routex
pickup the next delivery- This feature is included
- This feature is included
- This feature is included
- This feature is included
- This feature is not included
- This feature is not included
Schedulex
generate trips with delivery windows- This feature is included
- This feature is included
- This feature is included
- This feature is included
- This feature is not included
- This feature is not included
In some cases there may be no solutions or the computation will be terminated with a duration threshold, we make the best effort to provide results but it is not guaranteed all the time.
Currently released under limitations for evaluation.
Pricing is request-based in production environments.
Contact the team for volume-based pricing.