{"id":3874,"date":"2018-01-18T13:15:08","date_gmt":"2018-01-18T13:15:08","guid":{"rendered":"http:\/\/support.loginextsolutions.com\/?p=3874"},"modified":"2026-02-20T08:52:56","modified_gmt":"2026-02-20T08:52:56","slug":"route-planning-properties-2","status":"publish","type":"post","link":"https:\/\/support.loginextsolutions.com\/index.php\/2018\/01\/18\/route-planning-properties-2\/","title":{"rendered":"Trip Planning Properties\u2014Planning Profile"},"content":{"rendered":"\n\n\n\t<div class=\"dkpdf-button-container\" style=\" text-align:left \">\n\n\t\t<a class=\"dkpdf-button\" href=\"\/index.php\/wp-json\/wp\/v2\/posts\/3874?pdf=3874\" target=\"_blank\"><span class=\"dkpdf-button-icon\"><i class=\"fa fa-file-pdf-o\"><\/i><\/span> Download PDF<\/a>\n\n\t<\/div>\n\n\n\n\n\n<ul id=\"article-tab\">\n<li><a href=\"#\/2018\/01\/18\/route-planning-properties-2\/\">Desktop\/Laptop<\/a><\/li>\n<li><a href=\"#\/2023\/12\/27\/trip-planning-properties-planning-profile\/\">Mobile App<\/a><\/li>\n<\/ul>\n<p>Trip refers to a delivery associate\u2019s order fulfillment journey. Each trip is associated with a delivery associate. In one trip, there may be multiple orders for the delivery associate to fulfill depending on your configurations. The Trip Planning engine plans the most optimized trips for your delivery associates, based on a set of properties that constitute a Planning Profile. Within a Planning Profile, you can specify various parameters and select a number of properties to tailor trip planning for your operational requirements. There is already a pre-configured Planning Profile that you can use for your operations.\u00a0However, if you\u2019d like to customize the logic to suit your operations better, you can create more as needed.<\/p>\n<p>To create an optimized trip plan, all you need to do is select the orders and the fleet that should be considered for fulfilling those orders. The Trip Planning engine takes care of the rest.\u00a0Click\u00a0<a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2018\/01\/18\/create-route-plan-3\/\">here<\/a>\u00a0to learn more about how to create trip plans.<\/p>\n<h4><b>Auto-assignment vs Trip Planning<\/b><\/h4>\n<p>Generally speaking,\u00a0if you receive orders that need to be assigned right away, use the <a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2019\/03\/25\/auto-assignment-properties\/\">Auto-assignment<\/a> engine. Whereas, if you receive orders that need to be assigned as per a schedule, use the\u00a0Trip Planning\u00a0engine to automatically create and plan\u00a0the most optimized trips for your delivery associates.<\/p>\n<h4><b>Planning Profile<\/b><\/h4>\n<p>To create\/update a Planning Profile and configure the required properties, go to Settings &gt; Planning Profile.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-16060\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-11-19-215203-Copy.png\" alt=\"\" width=\"250\" height=\"244\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-11-19-215203-Copy.png 369w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-11-19-215203-Copy-300x293.png 300w\" sizes=\"(max-width: 250px) 100vw, 250px\" \/><\/p>\n<p>To create a new Planning Profile, continue to configure the properties as explained below, and then click Save As New to save those properties within a new Planning Profile. To update an existing Planning Profile, select that Profile from the Planning Profile drop-down, configure your properties, and then click Save.<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-13031\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-03-29-at-3.49.01-PM.png\" alt=\"\" width=\"851\" height=\"466\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-03-29-at-3.49.01-PM.png 2877w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-03-29-at-3.49.01-PM-300x164.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-03-29-at-3.49.01-PM-768x420.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2023-03-29-at-3.49.01-PM-1024x561.png 1024w\" sizes=\"(max-width: 851px) 100vw, 851px\" \/><\/p>\n<h4><strong>Trip Planning Properties<\/strong><\/h4>\n<p>There are several planning properties that you can configure to optimize your trip plans. These properties serve as constraints that the planning engine should consider while planning your orders.<br \/>\nThe planning properties are categorized into:<\/p>\n<ol>\n<li><u>Planning Objective:<\/u>\u00a0When planning the orders, you would want to achieve a goal rather than just plan orders. The goal can be to optimize overall trip cost or find the best possible route for fleet or to create trips which distributes the amount of work among the selected fleet. You can define this planning objective along with other constraints to achieve your planning goals. You can find details about the various objectives in\u00a0<a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2018\/01\/18\/planning-flavours\/\" target=\"_blank\" rel=\"noopener\">Planning Flavours<\/a>.<\/li>\n<li><u>Route Constraints:<\/u>\u00a0To achieve the goal, you may want to modify the various route constraints that can be applied to optimize the trips.<\/li>\n<li><u>Fleet Constraints:<\/u>\u00a0Along with the route constraints, you can also apply fleet constraints which are applied on the selected fleet to optimize the trips.<\/li>\n<li><u>Advanced:<\/u>\u00a0There are certain other operational constraints that you may want to apply that are available under this section.<\/li>\n<\/ol>\n<p>All of these 4 sections make a <b>Planning Profile<\/b>. You can create multiple planning profiles with different combinations of objectives and constraints. By using the planning profiles, there would be consistency in the trips that you create and will also save you time to configure each and every time you want to plan orders.<\/p>\n<h5><strong>Route Constraints<\/strong><\/h5>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-19308 \" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM.png\" alt=\"\" width=\"850\" height=\"443\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM.png 2219w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM-300x156.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM-1024x534.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM-768x400.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM-1536x801.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-04-22-at-12.52.06\u202fPM-2048x1068.png 2048w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><br \/>\nFollowing are the Route Constraints:<\/p>\n<ol>\n<li><u>Customer Address Considerations:<\/u>\u00a0Here, you can configure whether certain address-level details should be considered in planning.<br \/>\n1.1\u00a0Consider Customer Break Time:\u00a0While creating customers, you may have entered the customer&#8217;s break time. You can define whether the delivery associate can go to the customer&#8217;s location in break time. On enabling this, the planning engine will not send delivery associate when the customer is on break.<br \/>\n1.2 Consider Customer Service Time:\u00a0While creating customers, you may have entered the customer&#8217;s service time. When you enable this property,\u00a0the planning engine would add the service time defined at the order level and while creating the customer and take that as the total service time for the order. This will help the delivery associate to reach the customer on time.<br \/>\n1.3 Consider Location Restriction: While creating customers, you may have specified certain location restrictions against their addresses. (Location restrictions can be configured under the module Customer Configuration in Settings and then you can select specific location restrictions while creating\/updating customers).<span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">\u00a0<\/span><\/span><span style=\"font-weight: 400;\">Here, you can configure whether or not specific fleets with certain skill sets should be considered for these location restrictions during planning. To do so, click the pencil icon and select the necessary details from the drop-down menu, such as location restriction, field, operator, and value. In the &#8216;Location Restriction&#8217; field, select the configured restriction, and in the &#8216;Value&#8217; field, select the required skill set. In the &#8216;Operator&#8217; field, you can either select &#8216;is any of&#8217; or \u2018not in&#8217; values.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If you select &#8216;is any of&#8217; in the \u2018Operator\u2019 field, you can specify which fleets with skill sets matching those in the \u2018Value\u2019 field, are allowed to service the location restrictions.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conversely, if you select &#8216;not in,\u2019 you can specify which fleets with skill sets matching those in the \u2018Value\u2019 field, are restricted from servicing those locations.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Note that you can apply multiple constraints to the location restrictions by clicking the &#8216;Add More Restriction&#8217; button and specifying the necessary details.<br \/>\n<\/span><\/span>1.4 Prefer One Vehicle for Nearby Orders: Keeping this ON will give preference to assigning nearby orders to the same vehicle, in scenarios where an area can have similar location restrictions. Turning this OFF will let orders of nearby locations be assigned to the same or different vehicles. When enabled, the Set Geofence Radius field appears, where you can specify the radius within which orders should be assigned to the same vehicle.<\/li>\n<li><u>Consider Delivery Associate Availability and Order Time Window:<\/u>\u00a0Using this constraint, you can define whether you want to consider only the order time window or only delivery associate shift time or both.<\/li>\n<li><u>Return Back to Branch after Last Order Completion:<\/u>\u00a0Would you want your delivery associates to return to branch after the last order is completed. If yes, you can enable this constraint. When this constraint is enabled, the planning engine will consider the distance from the last order to branch and add it to the distance that the delivery associate can travel on the trip.<\/li>\n<li><u>Route Restrictions:<\/u>\u00a0Using this constraint, you can restrict certain routes delivery associates can take for a trip. You can restrict if the delivery associate can take highways, tollways, or ferries.<\/li>\n<li><u><span style=\"font-weight: 400;\">Consider Maximum Distance Cost<\/span>:<\/u>\u00a0You can set the maximum distance that the delivery associate can travel on a trip. Along with the maximum distance, you can also select if this distance has to be calculated from the branch or the first order. The planning engine will not assign more orders if the maximum distance is attained or adding a new order will breach the limit.<\/li>\n<li><span style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Maximum Number of Stops: <\/span><\/span><\/span>By enabling this constraint, you can set the maximum number of pickup\/delivery stops that can be made in a trip. <span style=\"font-weight: 400;\">By strategically limiting stops, you save valuable time and labor resources. This means faster routes and reduced parking slot searches, maximizing your fleet&#8217;s output and overall productivity.<br \/>\n<\/span>To do so, turn the toggle ON and input the maximum number of stops in the given field. You can control what shall constitute a stop:<br \/>\n-Customer Leg: To consider customer locations as stops, turn this toggle ON.<br \/>\n-Branch Leg: To consider branch locations as stops, turn this toggle ON.<br \/>\nIf both Customer Leg and Branch Leg are enabled, both customer and branch locations will be considered as stops. For example, if a delivery associate has to pick up 5 orders from a branch and deliver it to 5 different customers and both Customer Leg and Branch Leg are enabled, total stops would be counted as 6.<br \/>\nIt is also important to note that you can configure Maximum Stops for individual fleet types or individual delivery associates and vehicles as well. This functionality is available while adding fleet types, vehicles, and delivery associates to the system. Suppose you provide Maximum Stops for fleet types and these fleet types are, in turn, linked to delivery associates or vehicles. In that case, the delivery associates \/ vehicles inherit them from the attached fleet types. The Maximum Stops you provide here in the Planning Profile apply to all those delivery associates and vehicles that do not have these values defined for them specifically. That is, these are general settings that apply to all your fleet. If Maximum Stops are defined for individual vehicles or delivery associates, they will override the values you provide here.<br \/>\nNote:<br \/>\n-For Delivery Only accounts, only customer legs are considered as stops.<br \/>\n-A location at which multiple grouped orders are being picked up\/delivered will be counted as one stop for the delivery associate.<span style=\"font-weight: 400;\"><br \/>\n<\/span><\/li>\n<\/ol>\n<h5><strong>Fleet Constraints<\/strong><\/h5>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-21046\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM.png\" alt=\"\" width=\"851\" height=\"463\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM.png 2353w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM-300x163.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM-1024x557.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM-768x417.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM-1536x835.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2024-07-11-at-12.58.42\u202fPM-2048x1113.png 2048w\" sizes=\"(max-width: 851px) 100vw, 851px\" \/><br \/>\nFollowing are the Fleet Constraints:<\/p>\n<ol>\n<li><u>Postal Code Preference:<\/u> While creating delivery associates, you can define the postal codes that you would want to assign to delivery associates. Enabling this constraint, you can enforce that the delivery associate be assigned orders that match the postal codes assigned to the delivery associates. If you have custom territories, it is recommended not to enable this.<\/li>\n<li><span style=\"text-decoration: underline;\">Minimum Capacity Utilization:<\/span> Here you can specify whether Minimum Capacity Utilization parameters will be considered. To learn more about Minimum Capacity Utilization, click <a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2021\/09\/15\/fleet-configuration\/\">here<\/a>.<\/li>\n<li><span style=\"text-decoration: underline;\">Order Prioritization:<\/span>\u00a0<span style=\"font-weight: 400;\">By toggling this option, you can choose how your orders are prioritized during trip planning. You have three options: Order Priority, Original Time Window, and Updated Time Window. Order Priority corresponds to the value set in the \u2018Priority\u2019 field when the order is created, Original Time Window refers to the specified \u2018End Time\u2019 during order creation, and Updated Time Window refers to any subsequent changes to the \u2018End Time\u2019 after order creation. Based on your selection, the planning engine will prioritize the orders.<br \/>\n<\/span>While choosing Priority ensures that orders assigned higher priority values are prioritized, opting for Time Window options prioritizes orders with the <span style=\"font-weight: 400;\">nearest or lapsed end times.<br \/>\n<\/span><span style=\"font-weight: 400;\">Note that if you select either of the Time Window options and <\/span><span style=\"font-weight: 400;\">multiple orders share the same End Time, the system will prioritize those created earlier.<\/span><br \/>\n<span style=\"font-weight: 400;\">For instance, i<\/span><span style=\"font-weight: 400;\">f you have the following orders:<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">-Order 1 with a Priority of P2, originally scheduled to end at 5:00 PM, but later updated to end at 7:00 PM.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">-Order 2 with a Priority of P1 and originally scheduled to end at 6:00 PM, but later updated to end at 5:30 PM.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">(Where P1 represents the highest priority)<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">Now, if you choose the Order Prioritization options as follows:<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">&#8211; Priority: Order 2 will be prioritized over Order 1.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">&#8211; Original Time Window: Order 1 will be prioritized over Order 2.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">&#8211; Updated Time Window: Order 2 will be prioritized over Order 1.<\/span><\/li>\n<li><span style=\"text-decoration: underline;\">Capacity and Cost Parameters:<\/span> You can choose whether to consider the parameters defined for delivery associates or vehicles for planning trips. These parameters include Skill Sets, Minimum Capacity Utilization, Shift Start Time, Shift End Time, Break Start Time, Break End Time, Break Duration, Capacity, Fixed Cost, Variable Cost, Transporter Time Cost, Waiting Time Cost, Maximum Distance Per Day, <span style=\"font-weight: 400;\">Loading Time, and Maximum Stops.<\/span><br \/>\n<span style=\"font-weight: 400;\">Note: If you select \u2018vehicle\u2019:<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">&#8211; All the vehicles should be mapped to the relevant delivery associates.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">&#8211;\u00a0 If a vehicle is linked to multiple delivery associates, the system shows a message informing you that multiple people share the vehicle.<\/span><\/li>\n<li><u>Mode of Travel:<\/u>\u00a0This lets you define the mode of travel that your delivery associates use. You an select from 3 options, i.e., on foot, light commercial vehicle, and heavy-duty vehicle. Based on this selection, the planning engine will factor in the traveling speed of the delivery associate, as well as relevant\u00a0restrictions and considerations, to optimize the overall plan. Note that light commercial vehicles include cars, vans, two-wheelers, etc., whereas heavy-duty vehicles generally refer to trucks.<\/li>\n<li><span style=\"text-decoration: underline;\">Hours of Service Regulations:<\/span>\u00a0Enable this to ensure compliance with the Hours of Service Regulations that govern the activities of delivery associates of commercial goods carrying vehicles. You can configure daily on-duty time, off-duty time, and more such parameters. If this property is enabled in the Planning Profile, the ETA calculation algorithm also considers it in calculations.<\/li>\n<li><u>Consider Delivery Associate Skill-set:<\/u>\u00a0Can the orders be serviced by any delivery associate or do you want a planning engine to match the skill required for the order with that of the delivery associate and assign the order accordingly? When this constraint is ON, the planning engine would match the skill required by the order with the delivery associate. Note that if there is no skill mentioned in the order then any delivery associate can service the order.<\/li>\n<li><u>Resource Loading Time:<\/u>\u00a0While creating a delivery associate, you would have defined the time required to load orders. When this constraint is ON, the planning engine will consider the time taken to load orders.<\/li>\n<li><span style=\"text-decoration: underline;\">Resource Shift Time:<\/span> Enabling this property ensures that the Trip Planning engine considers the Shift Timings defined against the fleet. If the fleet doesn&#8217;t have any Shift Timings defined, then it is considered to be available 24 hours. Note that the Resource Shift Timing property should not be enabled in conjunction with the Hours of Service Regulations property.<\/li>\n<li><span style=\"text-decoration: underline;\"><span style=\"font-weight: 400;\">Consider Fleet Category:<\/span><\/span> <span style=\"font-weight: 400;\">Enable this property to consider the values defined in the \u2018Category\u2019 field of your fleets. T<\/span><span style=\"font-weight: 400;\">ailoring distance and time estimations to each category enhances precision in trip planning. When this property is enabled in the Planning Profile, the ETA calculation algorithm also takes it into account. If &#8216;Category&#8217; remains unspecified for any fleet, it defaults to car for trip planning purposes.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">Note that if this property is enabled, any selections made in the Mode of Travel property will no longer have any effect.<\/span><\/li>\n<\/ol>\n<h5><strong>Advanced<\/strong><\/h5>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone  wp-image-32082\" src=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM.png\" alt=\"\" width=\"851\" height=\"564\" srcset=\"https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM.png 2206w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM-300x199.png 300w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM-1024x680.png 1024w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM-768x510.png 768w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM-1536x1019.png 1536w, https:\/\/support.loginextsolutions.com\/wp-content\/uploads\/Screenshot-2026-02-20-at-2.16.16\u202fPM-2048x1359.png 2048w\" sizes=\"(max-width: 851px) 100vw, 851px\" \/><\/p>\n<p>Following are the Advanced constraints:<\/p>\n<ol>\n<li><u><strong>Capacity Optimisation Parameter<\/strong>:<\/u><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">Based on the nature of your operation, you can consider the number of orders as the maximum number of units that the delivery associate can carry in a trip or the number of items added in the orders as the maximum number of units carried by delivery associate in a trip.\u00a0<\/span>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Match number of Orders with the available Capacity of Delivery Associate: Capacity of Delivery Associate will be checked with respect to the total number of orders on a trip.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Match number of crates in an Order with the available Capacity of Delivery Associate: Capacity of Delivery Associate will be checked with respect to the number of crates in an order.<\/span>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Split large Orders<\/span>: The \u2018Match number of items in an Order with the available Capacity of Delivery Associate\u2019 property should be turned ON to enable all the configurations related to Split Order. If you have huge orders with more capacity than that of a vehicle or Delivery Associate then chances are that such orders will remain unassigned. With this property, you can now split your bulky order into smaller orders that can be fulfilled by the vehicles or Delivery Associates. The splitting will happen only on the basis of the number of crates in an order. By default, the smallest capacity of the vehicle or Delivery Associate is considered for dividing the order. For example, if you have vehicles with capacities of 9, 12, and 15 units and an order with a total of 18 crates then the smallest vehicle i.e. with the capacity of 9 units will be considered and the order will be split into 2 vehicles with 9 crates each.<\/span>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Define Order split threshold (number of Crates)<\/span>: The default capacity limit considered for an order splitting is the capacity of a vehicle or Delivery Associate with the smallest capacity. You can define a threshold to override this default value. If this value is set to more than 0 then the order will be divided on the basis of this value. For example, for an order of 18 crates if the threshold defined is 6 then the order will be split into 3 orders of 6 units each.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Assign all Orders split from a single large Order<\/span>: Turning this ON will ensure orders split from a single large order are not partially assigned, so if one of the split orders is unassigned, the entire large order remains unassigned. Eg. For an order having 10 crates and a capacity threshold set to 2, the orders created post-split would be 5. If even one of these orders remains unassigned due to resource constraint or any other factor then the rest of the 4 orders will also be left as unassigned. If this property is kept OFF then few orders will be assigned even if a few remain unassigned from the same huge order.<\/span><\/li>\n<\/ol>\n<\/li>\n<li><span style=\"text-decoration: underline;\">Consider Compartment to Assign Crates<\/span>:\u00a0<span style=\"font-weight: 400;\">If this property is turned OFF, the Trip Planning engine will consider the unit capacity of the fleet type \/ delivery associate \/ vehicle while assigning crates. Turning this ON will ensure that compartment-level configurations are factored in while Trip Planning, i.e., whether a crate is allowed in a compartment and the capacity of the compartment. <a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2022\/06\/23\/compartment-configuration\/\">Learn more<\/a>.<\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<li><u><strong>Orders with Elapsed Time-window<\/strong>:<\/u>\u00a0You can plan for orders whose time window is elapsed. Based on whether you want to plan orders with an elapsed time window or not, the planning engine would assign such orders on a trip or let them remain unassigned.<\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\"><strong><span style=\"text-decoration: underline;\">Pickup or Delivery Time Constraint at Branch<\/span><\/strong>: If you want to include the time taken for pickup from Branch and\/or deliver to Branch in the order start and end time window then set the time in minutes in the below 2 properties &#8211;<\/span>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Time interval for an Inbound order to reach the branch (in minutes): This is applicable for a Pickup type of an order.\u00a0<\/span><span style=\"font-weight: 400;\">If the pickup time window for an order is 09:00 &#8211; 11:00 am and the time interval defined for the branch is 15 minutes, the order will be planned to be delivered at the branch between 10:45 &#8211; 11:00 am. If not set or set to 0, then the pickup time window will be considered only for the pickup of the order.<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Time interval for an Outbound order to be dispatched from the branch for delivery (in minutes): This is applicable for a Delivery type of an order.\u00a0<\/span><span style=\"font-weight: 400;\">If the delivery time window for an order is 09:00 &#8211; 11:00 am and the time interval defined for the branch is 15 minutes, the order will be planned to be dispatched from the branch between 09:00 &#8211; 09:15 am. If not set or set to 0, then the delivery time window will be considered only for delivery of the order.<\/span><\/li>\n<\/ol>\n<\/li>\n<li><u><strong>Use Shared Fleet Pool for Higher Utilisation<\/strong>:<\/u>\u00a0In your operations, if you use your parent branch&#8217;s fleet, use this constraint. If enabled, his property\u00a0<span style=\"font-weight: 400;\">equally and impartially considers delivery associates from your parent branch (alongside the delivery associates from your own branch) to allocate your orders, ensuring equitable distribution of delivery associates without any hierarchical preference to parent or child branch. <\/span>If there is no fleet created for the branch and this constraint in ON, then the planning engine will consider the fleet of the parent branch.<\/li>\n<li><u><strong>Buffers<\/strong>:<\/u>\u00a0You might not be able to exactly define the time and capacity of delivery associates. In this constraint, you can define the time and capacity buffers.\n<ol>\n<li><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Planned Time Buffer (% of planned time per Order)<\/span>: You can set the buffer percentage that will be added to the planned transit time per order. Eg. If the planned transit time is 30 mins from location 1 to location 2, then adding a buffer of 50% will revise the transit time to 45 mins. It stretches the transit time required for the pickup or delivery of the order. The trip will be planned with these time constraints including the buffer without compromising on the order fulfillment time windows. The buffer for the transit time is set so that the planning of the trip is done such that the orders can be fulfilled in their respective time windows.<\/span><\/li>\n<li><span style=\"font-weight: 400;\"><span style=\"text-decoration: underline;\">Capacity Buffer (% of defined Capacity<\/span>): You can set the buffer percentage of the vehicle\u2019s capacity. Eg. If a vehicle has a capacity of 10 units and if the buffer is set to 50% of the defined capacity then the new capacity of that vehicle is 15 units.<\/span><\/li>\n<\/ol>\n<\/li>\n<li><span style=\"text-decoration: underline;\"><strong>Consider Branch Loading and Unloading Time<\/strong><\/span>: If this property is ON then the loading and unloading time at the branch will also be considered during the trip planning. The trip ETA will be impacted by the time taken by the Delivery Associate to load the orders before leaving the branch for order deliveries and also by the time taken by the Delivery Associate to unload the orders after reaching the branch after order pickups.<\/li>\n<li><span style=\"text-decoration: underline;\"><strong>AI Recommended Service Time:<\/strong><\/span> If you enable this property, the planning engine will take into account the AI-recommended service time, based on historical data.<\/li>\n<\/ol>\n<p><b>Additional Properties:<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Pickups and then Deliveries:<\/b><span style=\"font-weight: 400;\"> Enabling this property ensures that all orders are picked up first before any deliveries are made, preventing the pickup of new orders once the deliveries are started.<\/span><span style=\"font-weight: 400;\"> By default, this property is enabled for all planning profiles. To disable or re-enable it if previously disabled, <\/span><a href=\"https:\/\/support.loginextsolutions.com\/#\/2023\/02\/03\/log-a-ticket\/\"><span style=\"font-weight: 400;\">raise a support ticket<\/span><\/a><span style=\"font-weight: 400;\"> and provide the code \u2018USEPND\u2019.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Minimize multiple vehicles per location:<\/b><span style=\"font-weight: 400;\"> You can use a set of properties to ensure the minimum number of vehicles is used to serve multiple orders of a specific customer or multiple orders from various customers that are geographically located close to each other. By default, this is disabled for all planning profiles.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><span style=\"font-weight: 400;\">To enable or re-disable, simply <\/span><a href=\"https:\/\/support.loginextsolutions.com\/#\/2023\/02\/03\/log-a-ticket\/\"><span style=\"font-weight: 400;\">raise a support ticket<\/span><\/a><span style=\"font-weight: 400;\"> and provide the following:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">\u2018PENALIZE_MULTI_VEHICLE_PER_LOCATION\u2019: Specify the value for this as \u2018Y\u2019 to enable or \u2018N\u2019 to disable this property, along with the name of the planning profile for which you want to enable or disable this property.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">\u00a0\u2018LOCATION_MATCH\u2019: If you specify \u2018Y\u2019 for \u2018PENALIZE_MULTI_VEHICLE_PER_LOCATION\u2019, you will need to specify values for \u2018LOCATION_MATCH\u2019. Here, specify the location type for which you want to minimize the number of vehicles. You can either specify the value as \u2018Customer\u2019 to minimize vehicles for a particular customer or \u2018Coordinate\u2019 to minimize vehicles at specified location coordinates. For example,<\/span>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"3\"><span style=\"font-weight: 400;\">If you have three orders from the same customer, instead of assigning different vehicles for the same location, set the \u2018LOCATION_MATCH\u2019 as \u2018Customer\u2019. The planning engine will consider each customer address as one location and assign the minimum possible vehicles for all the orders from that customer.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"3\"><span style=\"font-weight: 400;\">If you have five orders from different customers that are geographically located near each other, set the \u2018LOCATION_MATCH\u2019 parameter as \u2018Coordinate\u2019. The planning engine will consider each set of coordinates as one location and assign the minimum possible vehicles for all orders from nearby customers.<\/span><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">\u2018LOCATION_MATCH_PRECISION\u2019: This parameter is only required when using the \u2018Coordinate\u2019 option. It further refines location matching precision for coordinates (i.e., latitude and longitude). You can specify the precision as either 4 or 5, where 4 represents an approximate area of 11 meters and 5 represents an area of 1 meter. (For example: 44.12345, 77.12345 signifies an area of 1 meter, while 44.1234, 77.1234 signifies an area of 11 meters.) The default value is set to 5, but for better accuracy, we recommend using four decimal places.<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><!-- Created with Elementor --><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Download PDF Desktop\/Laptop Mobile App Trip refers to a delivery associate\u2019s order fulfillment journey. Each trip is associated with a delivery associate. In one trip, there may be multiple orders for the delivery associate to fulfill depending on your configurations. &hellip; <a href=\"https:\/\/support.loginextsolutions.com\/index.php\/2018\/01\/18\/route-planning-properties-2\/\">Continued<\/a><\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[],"tags":[392,3020,3019,3018,3017,3014,3011,3010,438,437,400,399,398,397,253,371,370,369,368,367,366,365,364,363,362,361,255,254],"_links":{"self":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/3874"}],"collection":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/comments?post=3874"}],"version-history":[{"count":78,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/3874\/revisions"}],"predecessor-version":[{"id":32083,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/posts\/3874\/revisions\/32083"}],"wp:attachment":[{"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/media?parent=3874"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/categories?post=3874"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/support.loginextsolutions.com\/index.php\/wp-json\/wp\/v2\/tags?post=3874"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}