2 tours to same location at the same time

[Lauterfeld]

Hi together,

we had a bigger request with many ordery and transport points.
Every order has it's own transportpoint.
5 orders and its 5 transportpoints were at the same x,y so to speak the same customer.
xTour 1.22.0.2 planned 2 tours which arrived at the same time at that customer.
It was expected that xTour plans just one tour. All 5 orders could be planned in one tour (capacities and time windows and so on).
Is that cause of the 5 'independent' transport points? Would it be planned in 1 tour if we had one transport point and 5 orders?
Regards,
VL

[Bernd Welter]

Hello Volker,

from our understanding this shouldn't be a problem for the server.
I assume there is another reason for this behaviour.

Could you provide the XML request / response to (1:1 to me) for some analysis?
Furthermore: what happens if you restrict the request to allow not more than one tour?
Will then all the orders be scheduled?
If not: what is the output of the UnscheduledOrdersAnalysis?

Best regards Bernd

[Lauterfeld]

Hi Bernd,

we now know what our problem is, perhaps you have an idea...

We have 2 order, every order has its own transport point. Because we're not able to use the loading functions in the order to represent the service period of the order, we place them in the fixed service period of the transport point.
When we have a time window for example 2-3 pm and both transport points have service period of 15min, xTour will only place both order / points on the same tour when the truck arrives early enough to start the service of the second order, in our example 2:44:59 pm.
The arriving is calculated per order and point so xTour will split the 2 orders on different tours but in reality the arriving time of the first order is also good enough to unload the second order.
How can wie achieve that? Both points have the same siteid.

Regards,
Volker.

[Bernd Welter]

Forwarded to DEV as Issue 420

[Bernd Welter]

Hello Volker,

I just found this old task. Still relevant?

Not sure how to understand the latest part with the two orders but maybe we can take a look at the following two mechanisms:

• TransportPoint.openingIntervalConstraint being set to "start of service"
• aggregation of the service periods via SiteID

Maybe we can handle the story via a 1:1 call?
Or just give me a "not required anymore" here in the forum.

Best regards,
Bernd

[Bernd Welter]

cheers!

This topic deals with the same challenge...
https://xserver.ptvgroup.com/forum/view ... f=6&t=1147