{"id":7698,"date":"2019-01-30T13:12:04","date_gmt":"2019-01-30T13:12:04","guid":{"rendered":"https:\/\/support.loginextsolutions.com\/?p=7698"},"modified":"2026-01-28T09:42:48","modified_gmt":"2026-01-28T09:42:48","slug":"route-planning-pre-checks","status":"publish","type":"post","link":"https:\/\/support.loginextsolutions.com\/index.php\/2019\/01\/30\/route-planning-pre-checks\/","title":{"rendered":"Route Planning Pre-checks"},"content":{"rendered":"\n\n\n\t
\n\n\t\t<\/i><\/span> Download PDF<\/a>\n\n\t<\/div>\n\n\n\n\n\n\n

Planning is one of the prime functionalities which optimizes 16 parameters like Resource Capacity, Delivery distance, Time, Skill Set Type, etc. There is a lot that might happen while you plan and to make it easier for you, here is pretty much everything that you would need to check and prevent when you plan a route.<\/p>\n\n\n\n

    \n
  1. Avoid Branch Mismatch<\/u>: Check if the branch of order and resource is same. In case, your business does not require you to match the branch of the resource and order, please contact your assigned account manager to have the client property configured for you.<\/li>\n\n\n\n
  2. Avoid Delivery Type Mismatch<\/u>:  Check if the delivery type in both order and resources is the same. If you do not need delivery type, remove the same from both orders and resources.  Planning engine takes into account the selected Delivery Type for the order and assigns a matching delivery associate.There can be multiple delivery types at resource level, but a single type at order level. <\/li>\n\n\n\n
  3. Capacity of Resource and Order:<\/span> Do make sure that the capacity of resources is sufficient for the system to allocate the orders while planning. You might also want to check if the configured unit system at client level is in sync with the capacity defined at resource level and in your inputs. By default the capacity of resource in number of units is actually number of orders. For example, if there are 6 orders with 2 units each and a single resource with capacity 10 units, system would allocate all 6 orders. There is a client property which can be enabled to consider number of units and hence after enabling the property, number of orders assigned would be 5 in this case.<\/li>\n\n\n\n
  4. Trip Start Time<\/u>: You can configure if your trips should start at the Order Delivery Start Time of the first order in the delivery or pick up sequence or the trip starts so that the Delivery Associate reaches the first destination by the Order Delivery Start Time. For eg: If the time window of orders is 10 AM to 6 PM, trip start time can be such that either the trip dispatches early enough to reach the first order location by 10 AM or the trip starts at 10 AM itself. <\/li>\n\n\n\n
  5. Planning Algorithm<\/u>: This is one of the major keys in planning. There are 3 planning algorithms currently: HAVERSINE, OSRM and Google. Make sure you select the right planning algorithm for planning (preferably Google).<\/li>\n\n\n\n
  6. Speed Factor<\/u>: Speed factor is the speed considered while planning when the Planning Algorithm is HAVERSINE and OSRM. It is required to calculate ETA and time between two points. In case you need to check the current configuration of the Speed Factor or update it, please get in touch with your assigned account manager. In case your Planning algorithm is Google, speed factor is not considered. By default it considers driving speed, but there is a client property to choose walking speed with Google.<\/li>\n\n\n\n
  7. Capacity Buffer<\/u>: Capacity buffer allows you to set some margin on the Delivery Associate capacity so as to improve the overall utilization. In case you wish to check the current configuration or update the same, please get in touch with your assigned account manager. If the capacity buffer Is 1.2, the system will be considering 120% capacity at the time of planning to assign orders. <\/li>\n\n\n\n
  8. ETA buffer<\/u>: ETA buffer allows you to set some margin on categorizing deliveries as an on-time or delayed. If we set ETA buffer to 1.2, ETAs would increase by 20%. It is generally used when we have to average the speeds for bigger vehicles using Google algorithm. <\/li>\n\n\n\n
  9. Service-Time<\/u>: Service Time is the time spent by the Delivery Associate at the customer location the moment he stops at the customer location till the time it checks out to continue the trip. Since it is accounted by the system while planning, make sure the configured Service Time makes sense.<\/li>\n\n\n\n
  10. Time limit to re-plan the same orders<\/u>: This property defines the time limit before which the system doesn’t allow you to re-plan the orders. It is configured in minutes and if you configure 1440, system won’t allow you to plan the same orders before 24 hours. However, the unassigned orders while planning can be re-planned inside the limit.<\/li>\n\n\n\n
  11. Planning Flavor<\/u>: Currently, you can choose amongst two available planning flavors: Resource Optimization or Time-Distance Optimization. Resource optimization will only work when you have mentioned fixed cost and variable cost for the resource. Fixed cost (x) is at the resource level and variable costs (y) is calculated based on per distance unit. For instance, if 2 trips have been formed with total planned distance of 100 km, total planned cost after resource optimization would be 2x + 100y. Time-Distance Optimization ensures the route planned is the shortest and most optimized considering 16 different parameters like Delivery Type, Delivery Time Window, Delivery Associate Capacity, etc.<\/li>\n\n\n\n
  12. Consider Back to Hub<\/u>: If your operation require the delivery associate to return back to the hub after completing the trip, you would want to know the planned distance and ETA for the delivery associate from the last customer location to the hub or the branch. In this case the property should be configured for you.<\/li>\n\n\n\n
  13. Vehicle Capacity<\/u>: You can also plan optimizing the capacity of the vehicles configured in the Vehicle master by mapping those vehicles to the Delivery Associates. And configuring the property to consider vehicle capacity. In case the property is not configured, the planning will continue considering the capacity configured at Delivery Associate level.<\/li>\n\n\n\n
  14. Geofence Master:<\/u> Geofence let’s you assign designated territories to the Delivery Associates and plan as per the assigned territories. These are configured at the client level and any edits are reflected account wise irrespective of the branch. In case you are making use of this functionality, please do remember the following points before planning for the best experience.\n