Transit management

This page describes how to use Transit feature in Axiodis and corresponding key points.

Goals

Manage transit constraints for the system to be able to define automatically and / or manually which deliveries have to transited by a platform or have to be delivered directly to final logistics sites.

Transit route :

Delivery case: Turns from a point of origin (depot) to the cross-dock platform.
Collection case: Tour from one or more points of origin (usually logistics sites, suppliers, etc.) to the cross-dock platform.

Final route :

Delivery case: Tours from the cross-dock platform to one or more destination sites (usually logistics sites, stores, etc.).
Collection case: Tour from the cross-dock platform to a destination site (repository).

Note : Transit features must to be activated in the licence to be used.

Data and constraints

Define logistics sites as transit platforms is available in "Data and Constraints" module, "Logistic sites / Logistic sites" screen :

Manage constraints in transit platforms is available in "Data and Constraints" module, "Logistic sites / Transit platforms" screen :

For each transit platform, it's possible to define which logistics can be associated to apply a transit using corresponding options :

: Add logistics sites to the current platform
: Delete logistics sites from the current platform

Reference	Attribute	Description
1	Logistics sites	List of logistic site for which concern by the current platform transit. It is possible to assign logistics sites with one or several transit platform
2	Type	Type of the transit : Imposed or allowed Imposed : Transit by the platform is mandatory and the system will not be able to automatically propose another mode of transport (eg direct delivery of the site impossible). Allowed : Transit by the platform is possible but not mandatory and the system can make an arbitrage to propose automatically the most suitable mode of transport (ex: direct delivery of the site or delivery with transit via the platform).
3	Product families	Possible specialization of the transit on one or several families of product to carry out the transit If none product family is defined for the transit platform, then it will be able to receive all products from the defined logistics site. If one or more product families are defined for the transit platform, then it can only receive products from the product families defined for the logistics site.
4	Weight maximal to transit	Quantities of weight in Axiodis : beyond this quantity, transit is no longer applied by the soler For a mandatory transit from the current site to the current platform, if the total quantity UP to be delivered to this site, any product merged, is greater than this value, then the system does not make the transit yet mandatory, and will deliver directly. It is enough that one of these 2 thresholds (volume / weight) is exceeded for that one cancels the obligatory transit.
5	Volume maximal to transit	Idem line 4 but applied for volume quantity
6	Creation of final operation	When a transit is apply on this transit platform, the system must create the final operation : Transit platform → client site (delivery context) Transit platform → depot site (collection context) If the option is checked, the system automatically creates the final operation. If the option is not checked, the system does not create the final operation
7	Minimum time limit	The minimum time is the minimum time to wait before the departure of the transit platform to the customer site (change of vehicle, unloading - loading ...) / deposit site
8	Maximum time limit	The maximum time limit is the maximum time to wait before the departure of the transit platform to the customer site (change of vehicle, unloading - loading ...) / deposit site

Planning module

www.maplink.global