Understanding the TMS Allocation Engine
- eknoor.singh (Unlicensed)
Analytics
Selecting Consignment Notes
The journey begins with users choosing the Consignment Notes (CNs) they want to create routes for. They simply select the relevant CNs and click on the "Create Route" button.
Sending Request to the Optimiser
After selecting the CNs, a request is dispatched to the optimization engine, which plays a pivotal role in planning the most efficient routes. This request is comprehensive, including essential information:
Vehicle makes of the dedicated vehicles available for route planning.
Vehicle makes associated with vendors servicing both the origin and destination of the CNs, communicated via a constraints tag.
The optimisation engine then works its magic, generating trips based on predefined thresholds found in the freight configuration (
flm_freight_config).
Prioritising Dedicated Vehicles
In the allocation of Full Truck Load (FTL) trips, a crucial decision is made. Dedicated vehicles are accorded priority over pushing indents to vendors. This prioritisation is adjustable, granting the system the autonomy to determine whether dedicated vehicles should be assigned trips. If dedicated vehicles aren't prioritised, they won't be assigned any trips.
Handling Partial Truck Load Trips
CNs that are allocated to PTL trips follow a different route. They are removed from the planning process and remain in the unplanned bucket.
The Allocation Engine
The allocation engine takes over, responsible for the fair distribution of trips among eligible vendors. It relies on various components:
Trip Dimensions: Trips are defined by their distinct characteristics, including the Origin-Destination (OD) pair, route, and trip type (PTL or FTL).
Vendors Considered: The system identifies vendors eligible to serve the assigned routes.
Filters: Filters are applied to further fine-tune the allocation process, taking into account factors like specific vehicle makes or declared values.
Prioritisation: Vendors are prioritised based on certain criteria, falling into two categories:
Business-driven: Selecting the most cost-effective vendor based on financial factors.
Static: Prioritisation guided by predetermined criteria.
Constraints
Constraints come into play to ensure equitable allocation. These constraints are designed to control the maximum number of trips assigned to a vendor for a specific vehicle make. These constraints are configured in Transport > Vendor > Vehicle Make and count.
Indent Allocation
The system initiates the allocation of trips to vendors, commencing with the primary vendor (P1). If the primary vendor accepts the indent, the trip is assigned. Should they decline, the system proceeds to the secondary vendor (P2), and this process continues until an eligible vendor accepts the indent.
Unaccepted Indents
In cases where no eligible vendor accepts the indent, the trip remains in the Trip Manager, providing visibility into the current vendor and the indent's status (whether it's assigned, accepted, or rejected).
Static Priority Removal
The static priority, which was formerly defined in Transport > Vendor > New/Edit Vendor, is not utilised in this allocation engine.
Serviceability, TAT and Rate Masters
Key data elements such as serviceability, Turnaround Time (TAT), and rate master definitions are managed through masters within Carrier Account Integrations. These masters offer crucial insights for informed decision-making during the allocation process. They play a significant role in selecting the most suitable vendor for each trip, factoring in service levels, transit times, and pricing considerations.
In summary, this comprehensive logistics system involves an intricate process of route creation, trip allocation, and vendor prioritisation. The flexibility to prioritise dedicated vehicles, advanced allocation rules, and the consideration of various parameters like vehicle makes and vendor constraints all contribute to an efficient and dynamic logistics operation.