This forum deals with any kind of trip optimization based on xTour1, xTour2 and the Developer APIs "RouteOptimization" and "SequenceOptimization". No matter whether it is automatic planning or manual dispatching, refering to transport orders or service planning.
Attention: this does not refer to PTV Optiflow SaaS and PTV Developer RouteOptimization Optiflow.
Step#1:
We have created several tours (chains) with some planBasicTours-Requests from huge workload by complex and different preselects.
Step#2:
Now we like to invoke an improvement run of planBasicTours where the plan-in consists of all the chains calculated by step#1.
As we know that a planBasicTours with a plan-in w/o additional unscheduled orders in order-input will only check the feasibility of the given tours. I like to know how to call planBasicTours for step#2 - if possible .
Target is that xTour reassigns some orders from one tour to another if this leads to "better" chains (tours).
In step #1 you scheduled a set of orders 1,2,...n and created chains/tours for a set of vehicles.
Meanwhile some more UNSCHEDULED orders have been created and you'd like to add them to the existing tours (or to be more precise: chains).
It is an option that single scheduled orders are moved from their existing tour to another tour.
Well if this description is proper you should consider the following approaches / parameters:
if you want to allow swapping of orders from one tour to another tour you should consider StandardParams class as the required scenario parameter. Improvement phase enabled.
If you want to keep existing tour sets and only add further unscheduled stops to given tours AmendingParams is the correct way.
Besides those options of the PlanningParams you may have a look at the properties of your input tours and stops:
You can describe different levels of possible manipulations to input objects:
For example you can open the manipulations of a given tour to NONE (=worst case complete tour dissapears after IMPROVEMENT) but fix a specific tour point by setting tourFixed=true.
I hope this info helps you - if not: let me know what is missing!
Seems that your summary do not describe my intentions - lets try again:
From the huge workload we preselect (filter) unscheduled orders by certain criterias and start planBasicTours. Now we change some criterias for the preselect (-> getting other unscheduled orders from workload) and start a new planBasicTours.
After n-runs (based on different sets of criterias) we have m chains/tours.
By-the-way: all runs are without a plan-in!
Here ends step#1!
Now we like to request planBasicTours without unscheduled orders but WITH the m chains/tours from step#1 as plan-in!
We would like to get the improved set of chains/tours - if there is potential for "better" chains/tours by reassigning some orders from one tour to another.
By my first vision I think your first answer do not cover my scenario. Perhaps we are disjunct due to my wording: workload means unscheduled orders in my application - not TransportOrders in xTour.
ok, meanwhile I had a phonesession to get more details about this topic - looks like there is potential for misunderstanding. Let me summarize what we've been talking about:
The global setting is based on large number of orders and a heterogeneous fleet (expensive and less expensive vehicles with various "constraints").
With a first function call the "demanding" orders are assigned to the "expensive" vehicles (where there is no alternative). Let's call the output Output1.1. This output contains Chains1.1
With a second call based on "less expensive vehicles" and "some more orders" (except for the ones that are part of Output1.1) we generate some more chains Chains1.2
now from my understanding the question is: how can we combine the two Chainsets Chain1.1 and Chain1.2 and reduce required ressources? By using StandardParams (Improvement=true) and the scheduled orders of Output1.1 and Output 1.2 and an input plan based on Chains1.1+Chains1.2 where the manipulation level of the input tours is most flexible.
All input orders are part of input tours. All input vehicles are assigned to at least 1 tour. There are no unscheduled orders.
From my point of view this call will try to reduce the tours if possible - depending on the GOALs that are defined in the StandardParams.
.