vehicleRequirements and transportEquipments

[puissancei]

Hello,

To understand correctly.

witch vehicle is possibble in the case bellow ?

V1 : vehicleRequirements (1)
V2 : vehicleRequirements (1,2)
V3 : vehicleRequirements (1,2,3, 4)
V4 : vehicleRequirements (1, 20, 30)
V4 : vehicleRequirements (1,2,3, 4, 50, 60)

and

T : transportEquipments (1,2,3,4)

Thank you

[Bernd Welter]

Hello Michel,

the answer is:
V3 : vehicleRequirements (1,2,3, 4)
V4 : vehicleRequirements (1,2,3, 4, 50, 60)

No rocket science
Each INT mentioned in the TASK's array has to be available at the VEHICLE's array.

Best regards,
Bernd

[puissancei]

How does it happen if I want a TransportEquipment (A, B, C) to be delivered by a Category A or Category B vehicle or Category C vehicle (not all three at one time but one or two at a time only)


TransportEquipment (A, B, C)

with

vehicle 1 (A) = OK
vehicle 2 (B) = OK
vehicle 3 (A, B) = OK
vehicle 4 (A, B, C) = OK
vehicle 5 (A, Z) = OK
vehicle 1 (X, Y) = KO (of course)

[Bernd Welter]

Hello Michel,

sounds like you need some OR combination while our approach is based on AND.
From my perspective you have to solve this on application level combined with parameters:

• define a temporary equipment "dingelhopper" within your application.
• transfer to xTour: each vehicle that satisfies "A or B or C" is said to provide the "dingelhopper"
• transfer to xTour: an order that is happy with "A or B or C" is said to require a "dingelhopper"
• less convenient as the native way but with no loss of performance

That's it,

best regards from Bernd

[puissancei]

Hello,

thank you for your answer.

My approche.

TransportEquipment (A = 1, B = 2, C = 4 / AB = 3, AC = 5, BC = 6, ABC = 7)

vehicle 1 (A = 1) = OK
vehicle 2 (B = 2) = OK
vehicle 3 (AB = 6) = OK
vehicle 4 (ABC = 7) = OK
vehicle 5 (AD = 9) = KO

do you think it is applicable ?

[Bernd Welter]

Hello Michel,

I understand your approach and I have doubts whether it is helpful to work like that.
You model the skills as some kind of bitwise addition but how to deal with the ORDER side then?

Do you mean to set the "requirement = 6" to indicate that "B or C" are required?
How to understand your list of OK / not OK?

I recommend that you discuss this 1:1 with PTVs consulting.

Regards
Bernd

[Bernd Welter]

Just spoke to a colleague in NL. He has some customers with same usecase and he used CATEGORIES for that.

• Each vehicle is his own category
• For each order you can decide what vehicles (=category) is a match
• The orders category array is filled with the vehicles (=categories)

So with your initial example order requires (A,B,C) = "A or B or C"
vehicle 1 (A) = OK
vehicle 2 (B) = OK
vehicle 3 (A, B) = OK
vehicle 4 (A, B, C) = OK
vehicle 5 (A, Z) = OK
vehicle 6 (X, Y) = KO (of course)

order.vehicleCategories = {1,2,3,4,5}

The reason why I didn't mention this approach from the beginning was because categories are designed to slice a fleet into disjunct "categories" such as "small"<=>"medium"<=>"large".

Does this answer your question then ?

Best regards,
Bernd

[puissancei]

Hello,

I think it can resolve my problem.

Thank you