/
Manual and Automatic Trip Creation for Vendors

Manual and Automatic Trip Creation for Vendors

Creating a Trip

Creating a trip can be done in multiple ways:

  1. The first, and the simplest way to create a trip is by creating a custom trip.

    1. Here, the user will have options between creating a trip for all available consignments, creating a trip for just the selected or filtered consignments, uploading consignments and creating a trip for those, or bulk creating a trip by uploading a csv file.

    2. In either scenario, manual creation will prompt the user to input a few important details before trip creation is successfully completed.

  1. Another way of creating a trip is by navigating to consignments > unplanned > create route and begin the trip creation process. Once the user selects whether they want to create a route for all/selected/filtered consignments, a prompt appears where the user will have to input the trip start time. Post that, the following things will take place in the background:

Request Sent to Optimiser

The request sent to the optimiser will have:

  1. Vehicle makes of the dedicated vehicles available for planning i.e. not assigned to any trip

  2. Vehicle makes ( belonging to vendors) which service the origin and the destination of the CNs selected for optimised trips. Serviceability will come from the Carrier Partner ā†’ Carrier Account Integrations ā†’ Carrier Account ā†’ Serviceability Master. The master will have serviceability at OD pair and vehicle make level. The eligible vehicle makes for each CN will be sent at a CN level and will be passed via constraints tag to the optimiser.

  3. The destination city of the CN will also be pushed in the constraints tag of the optimiser. This will ensure that the created trips have the same destination city

Optimiser Output

  1. Optimiser output will give the list of trips with the following information

    1. Vehicle make

    2. Trip type (FTL/PTL) basis then the thresholds defined in internal configs (which will be defined by your POC at Shipsy)

    3. Assumption here is that optimiser will assign trips/CNs to vehicle makes which are eligible for for the OD pair of the CNs as per serviceability master

  2. Output essentially will be set of trips with vehicle make and trip type (FTL/PTL) basis the flm_freight_config

Handling of FTL and PTL Trips

  1. By default the FTL trips are assigned to the dedicated vehicles first and then indents are pushed to the vendors.

  2. By default the PTL trips are assigned to the dedicated vehicles first and then indents are pushed to the vendors .Ā 

Related content

Understanding the TMS Allocation Engine
Understanding the TMS Allocation Engine
Read with this
Customer POD Upload
Customer POD Upload
Read with this
User Level Debugging Guide
User Level Debugging Guide
Read with this
Hyperlocal Auto Allocation
Hyperlocal Auto Allocation
Read with this
Rate, Serviceability and TAT Masters
Rate, Serviceability and TAT Masters
Read with this
How to set up sorting configurations
How to set up sorting configurations
Read with this