Page 1 of 1

mixed loading prohibition: split orders into truck versus trailer

Posted: Tue Feb 04, 2025 9:31 am
by Bernd Welter
Hi there,
one of my partners is dealng with an xtour2 challenge that sounds like he could benefit from the mixed loading prohibition (com.ptvgroup.xserver.xtour.MixedLoadingProhibition:
Defines restrictions regarding which categories of orders are disallowed to be mixed on the same trip.
Here's the sample input and also the requested output. From my perspective the MixedLOadingProhibition does not cover this. Therefore the question is: is there an alternative approach?

Given:
  • Order 1: a predator
  • Order 2: a prey
  • conflictingCategory1="predator" , conflictingCategory2 = "prey"
Now the prohibition would cause the two orders to be dispatched to either
  • same vehicle but distinct trips
  • different vehicles / tours
What we could imagine as a possible structure:
  • predator on the truck
  • prey on the trailer
My two questions are:
  • Is there some workaround to achieve this given result based on a minimal sample
  • If the answer is positive: is this a generic approach that can also work with more orders (truck="meat, goat", trailer="tiger, salad")?
Bernd

Re: mixed loading prohibition: split orders into truck versus trailer

Posted: Tue Feb 04, 2025 7:09 pm
by Bernd Welter
In the context of
  • xTour2
  • PTV Developer RouteOptimization API (MAINTENANCE!)
  • PTV Developer SequenceOptimization API (MAINTENANCE!)
The answer is "not possible"...

For a statement in the context of
  • PTV Developer RouteOptimization OptiFlow
I requested the competence center to respond...

Stay tuned!

Bernd

Re: mixed loading prohibition: split orders into truck versus trailer

Posted: Thu Apr 03, 2025 12:30 pm
by TimDeMeerleer
In Route Optimization OptiFlow API this can be achieved via Loading Incompatibilities

Where the combination Flammable + Inflammable is this exact use case.

Re: mixed loading prohibition: split orders into truck versus trailer

Posted: Fri Apr 04, 2025 10:04 am
by Bernd Welter
Hi Tim,

Thanks for your answer. I am not sure whether I got this correct in terms of the Route Optimization Optiflow API...
The constraints there are designed to ensure that some product categories do not appear on a vehicle at the same time.

The customer doesn't want to exclude this in general - he just wants to make sure that the critical categories are not on the same section of the vehicle (truck <=> trailer). Maybe this is supposed to be resolved with compartments or loads?

Bernd