[tailsjt]

Hi there, i am trying to configure a multi leg scenario. I am attaching the flow of what I require. Essentially, I have 5 orders leaving different locations in italy, these need to be consolidated into 1 TL shipment that goes to a port. an ocean leg then goes from the port in italy to algeciras in spain, and then another ocean leg from algeciras in spain before meeting up with other shipments for onward destinations in russia. I have all the legs working with all the voyages correct, however my problem is that I cant get the 5 orders consolidating into 1 TL shipment at a hub, I can only get them sent straight to the port and for the port to consolidate which isnt what I need. I have setup smaller test scenarios and got consolidation and deconsoliation hubs working on their own so its not the setup on that side that is the problem, it is merging both setups together! To allow the hubs to work on their own I know I have to tick multistop itinerary, however when I come to do this on the itinerary for the larger flow it wont let me tick "multistop itinerary" because I have more than 1 leg. is there a way around this as you must be able to have consolidation/deconsolidation hubs as well as multi-legs?

Regards

Steve

[arunk]

Steve,

I can understand from your post that you want to execute a consol/deconsol scenario using a multileg itinerary and ways this can be done.

My answer to this is, Yes you can have consol/deconsol hubs using a multileg itinerary.

Say you have orders flowing from 3 different locations A,B,C to a consolidation hub D and from D it get consolidated and sent to another location E and from there to another.

Consider that the orders from A,B,C are LTL's to hub D and from D-->E TL and from
E-->any location with vessel or rail or anyother.

Your itineary shld be a mulitleg and you have to define 3 different legs to satisfy the above said scenario.

Your first leg will be of LTL to define the 3 LTL's from A,B,C to D.

Second leg would be of TL from D-->E and third would be vessel or rail from E-->any loc.

You need to mention the location role as CONSOLIDATION POOL and your consol hub in the location id in the first leg of your itinerary.

In the second leg, have the Equipment Assign Type as "Optimize Equipment" and Auto Consolidation Type as "CONSOL INTO ONE EQUIP".

Make sure you set the location role of D to consolidation hub in the locations. And have an equipment at D with proper weights, to accomodate all the multiple orders into one.

Also you can constrain the Orders by checking the "Must Ship thro POol" check box in the Order Release.

Kindly let me know if this is address your question.

Regds
Arun.

[Kiseleva]

Hi Arun!
I have exactly the same scenario but I've started from easier example. First of all I managed to plan shipments from A,B to hub C and then consolidated shipment from C-->D. There was not problem, but then when I tried to add one more leg I couldn't do it.
In the first leg I define hub C as a Cross Dock Location and location D as destination location for the leg. Second leg has destination F.
As a result system didn't use hub C in planning - I got four shipments: A-->D, D-->F, B-->D, D-->F.
But I expected to get A-->C, B-->C, C-->D, D-->F
May be you know what's wrong?

[arunk]

Originally Posted by Kiseleva

Hi Arun!
I have exactly the same scenario but I've started from easier example. First of all I managed to plan shipments from A,B to hub C and then consolidated shipment from C-->D. There was not problem, but then when I tried to add one more leg I couldn't do it.
In the first leg I define hub C as a Cross Dock Location and location D as destination location for the leg. Second leg has destination F.
As a result system didn't use hub C in planning - I got four shipments: A-->D, D-->F, B-->D, D-->F.
But I expected to get A-->C, B-->C, C-->D, D-->F
May be you know what's wrong?

Did you tried constraining the Order Releases by checking the "Must Ship Thro Pool" checkbox?

[Kiseleva]

Yes, I did

[arunk]

Kiseleva,

I would suggest you to create a multileg itinerary with three legs from A,B--->C (Consolidation pool), C--->D and D--->F.

Make the location role as CONSOLIDATION POOL and your consolidation hub C in the location id of the first leg in your itinerary.In the second leg, have the Equipment Assign Type as "Optimize Equipment" and Auto Consolidation Type as "CONSOL INTO ONE EQUIP".

Moreover I dont find any valid business reason to use X-Dock for your scenario, multiple sources and a single destination and i would prefer using a Consolidation rather than a X-Dock.

[Kiseleva]

Hi Arun!
I agree with you that in this scenario better to use Consolidation Pool. I've created Itinerary as you described. The result of planning is following - on second leg I get two shipments but I expected ONE. Auto Consolidation Type='consol into one equipment' on second leg. Third leg is single - it's ok.

[arunk]

Originally Posted by Kiseleva

Hi Arun!
I agree with you that in this scenario better to use Consolidation Pool. I've created Itinerary as you described. The result of planning is following - on second leg I get two shipments but I expected ONE. Auto Consolidation Type='consol into one equipment' on second leg. Third leg is single - it's ok.

Mean to say that it is creating two shipments A--->D and B--->D without getting consolidated in the pool C ?

If so, wondering how does it getting consolidated into a single one at thrid leg, D--->F.

Make sure your equipments has enough capacity to accomodate all the multiple orders into one. Your location role has been changed to Consolidation Pool nt as X-Dock.
Also Equipment assignment type of "Optimize Equipment" and Auto Consolidation Type='consol into one equipment', makes your two independent to get consolidated into a single one.

[Kiseleva]

No, I mean that I get 5 shipments totaly: A--->C, B--->C, C--->D, C--->D and D--->F.
Why C--->D is not consolidated I wonder? I used Consolidation Pool role for first leg.

[arunk]

If possible send me the screenshots of your itinerary leg configurations, i'll have a look on that. Iam sure you might have missed out something, becoz its getting consolidated in the location D instead of C.