Examples of the execution of the load building process

These examples show the results of each step that the load building engine takes to create loads and shipments from a group of freight orders. Combined freight orders, created during the first step, and stops and trips, created during the second step, are intermediate data which are used to analyze the real planning results, the loads and shipments created in the final step. First, the input data is shown for which load plans are created. The input data includes the following information:

  • Two sets of freight orders
  • The transport means groups selected to transport the goods listed on both sets of freight orders
  • The carriers that will transport the goods
  • The standard route and the route plan that the carriers travel to transport the goods
  • The distances and travelling times between the loading and unloading addresses of both sets of freight orders

For the first set of freight orders, load plans are created using the direct shipping and the consolidation planning methods. For the second set of freight orders, a load plan is created using the pooling planning method.

Input data

For the following freight orders, load plan 1 is created using the direct shipping planning method, and load plan 2 is created using the consolidation planning method:

Freight orderShip-from addressShip-to addressLoad datesUnload datesItem
001Own warehouseCustomer AEarliest11-21-03 07:0011-21-03 08:00100 monitors
Planned11-21-03 08:0011-21-03 11:00
Latest11-21-03 22:0011-21-03 22:00
002Own warehouseCustomer BEarliest11-21-03 07:0011-21-03 08:00120 monitors
Planned11-21-03 08:0011-21-03 11:00
Latest11-21-03 22:0011-21-03 23:00
003Own warehouseCustomer AEarliest11-21-03 07:0011-21-03 08:00100 keyboards
Planned11-21-03 08:0011-21-03 11:00
Latest11-21-03 22:0011-21-03 22:00

 

For freight orders 001, 002, and 003, the following carrier is available:

CarrierTransport means groupAverage speed
Speedex Int LtdTR1-Trucks 40m²100 km/h

 

For load plan 2, standard route OW-A-B is used. This standard route covers the addresses where the Own Warehouse, customer A, and Customer B are located.

For the following freight orders, load plan 3 is created using the pooling planning method:

Freight orderShip-from addressShip-to addressLoad datesUnload datesItem
004Own warehouse, The Hague, The NetherlandsCustomer C, Luton, United KingdomEarliest11-21-03 07:0011-22-03 08:00100 monitors
Planned11-21-03 08:0011-22-03 09:00
Latest11-21-03 22:0011-22-03 17:00
005Supplier's warehouse, Amsterdam, The NetherlandsCustomer D, Windsor, United KingdomEarliest11-21-03 07:0011-22-03 08:00120 monitors
Planned11-21-03 08:0011-22-03 09:00
Latest11-21-03 21:0011-22-03 17:00

 

For freight orders 004 and 005, route plan CH-SE, Central Holland - South England is used. This route plan includes the following legs:

Leg typeOrigin addressDestination addressDistance
AdvanceBGN00234The Hague, NetherlandsBGN04223Rotterdam Sea Terminal45 km
AdvanceBGN00289Amsterdam, NetherlandsBGN04223Rotterdam Sea Terminal65 km
MainBGN04223Rotterdam Sea TerminalBGN82266Sheerness Sea Terminal, UK350 km
BeyondBGN82266Sheerness Sea Terminal, UKCGB20036Luton, UK100 km
BeyondBGN82266Sheerness Sea Terminal, UKCGB21458Windsor, UK95 km

 

Freight order 004 goes from The Hague to Rotterdam by truck. Freight order 005 goes from Amsterdam to Rotterdam by truck. In Rotterdam, both freight orders are loaded in a cargo ship that takes them to Sheerness, United Kingdom. In Sheerness, the goods are loaded onto trucks that take freight order 004 to Luton and freight order 005 to Windsor.

For freight orders 004 and 005, the following carriers are available:

CarrierTransport means groupAverage speed
Speedex Int BVTR1-Trucks 40m²100 km/h
TransIt LtdTR1-Trucks 40m²100 km/h
Overseas LtdCV1- cargo ships30 km/h

 

Speedex Int BV carries out the transportation from The Hague and Amsterdam and Rotterdam. Overseas Ltd. takes the goods across the North Sea from Rotterdam to Sheerness, and TransIt Ltd. takes care of the UK part of the transportation.

For the freight orders in this example, the distances and travel times between the loading and the unloading addresses are as follows:

Distances
FromToKmTravel time
Own warehouseCustomer A1321 hour, 19 minutes
Customer ACustomer B4024 minutes
Own warehouseCustomer B1451 hour, 27 minutes
Own warehouseCustomer C49513 hours, 7 minutes
Supplier's warehouseCustomer D51013 hours, 16 minutes

 

The travel times are derived from the distances and the average speed of the transport means groups.

Note

For the sake of simplicity, times for loading and unloading, and waiting times for loading and unloading are not used in these examples.

Combined freight orders

The first step that the load building engine carries out to create shipments and loads from freight orders, is creating combined freight orders. This entails grouping freight order lines by load/unload addresses, time windows, and a few other attributes, which are explained in The load building process.

If load building is carried out for freight orders 001, 002, and 003, the load building engine creates the following combined freight orders:

Freight orders 001, 002, and 003: Load plan 1 direct shipping and load plan 2 consolidation
Combined freight orderShip-from addressShip-to addressPlanned load datePlanned unload dateCombined freight order lines
Freight order/lineItem
100001Own warehouseCustomer A11-21-03 08:0011-21-03 11:00001/10100 monitors
003/10100 keyboards
100002Own warehouseCustomer B11-21-03 08:0011-21-03 11:00002/10120 monitors

 

This table shows the most important data of the combined freight orders, the Combined Freight Orders (fmlbd1520m000) session shows more details. The freight order lines of freight orders 001 and 003 are combined into combined freight order 100001, because the loading/unloading dates, the loading/unloading addresses, and the other properties of the order lines match.

Note

The planning methods used bear no influence on the way the freight orders are combined. Therefore, freight orders 001, 002, and 003 are combined the same way, no matter whether you use the direct shipping, consolidation, or pooling planning method.

Freight orders 004 and 005: Load plan 3 pooling

If a load plan is created for freight orders 004 and 005, the following combined freight orders are created:

Combined freight orderShip-from addressShip-to addressPlanned load datePlanned unload dateCombined freight order lines
Freight order/lineItem
100001Own warehouseCustomer C11-21-03 08:0011-22-03 09:00004/10100 monitors
100002Supplier's warehouseCustomer D11-21-03 08:0011-22-03 09:00005/10120 monitors

 

This table shows the most important data of the combined freight orders, the Combined Freight Orders (fmlbd1520m000) session shows more details. For freight order 004 and 005 separate freight orders were created, because the loading/unloading dates, the addresses, and the other properties of the order lines of these freight orders do not match.

Stops and trips

The second step of the load building process is creating stops and trips from the combined freight orders.

Freight orders 001, 002, and 003: Load plan 1 direct shipping

For load plan 1, the load building engine creates the following trips and stops:

TripCarrierTransport means group
000000000150Speedex Int BVTR1 Trucks 40m²
000000000151Speedex Int BVTR1 Trucks 40m²

 

Trips are displayed in the Trips (fmlbd2500m000) session.

The carrier is selected because it is available according to its calendar and the calendar of the loading and unloading addresses, and because it matches the criteria of the Carrier/LSP Selection Criterion used for the load plan.

The transport means group is selected because it is attached to the selected carrier and because the properties of the transport means group and the items on the freight order lines, such as Combination Code or Transport Type, do not conflict. For further information on the Carrier/LSP Selection Criterion, see Freight Planning Parameters (fmlbd0100m000). In this example, a carrier and a transport means group was not entered on the freight orders or the freight order lines.

For trip 000000000150, LN created stop code 100000000001. Stop code 100000000001 includes a load stop and an unload stop. For trip 000000000151, LN created stop code 100000000002. Stop code 100000000002 includes a load stop and an unload stop.

Stops are displayed in the Stops (fmlbd1500m000) session.

Load planLoad plan 1 direct shipping
Stop code100000000001
Trip000000000150
Stop typeAddressMinimum load/unload dateMaximum load/unload dateOptimal date
LoadOwn warehouse11-21-03 07:0011-21-03 20:4011-21-03 09:40
UnloadCustomer A11-21-03 08:1911-21-03 22:0011-21-03 10:59

 

Note

In LN, fractions of minutes are rounded downwards. For example, a travel time of 01:19:20 becomes 01:19. This conversion has a minor impact on planning calculations.

Load planLoad plan 1 direct shipping
Stop code100000000002
Trip000000000151
Stop typeAddressMinimum load/unload dateMaximum load/unload dateOptimal date
LoadOwn warehouse11-21-03 07:0011-21-03 21:3311-21-03 09:33
UnloadCustomer A11-21-03 08:2711-21-03 23:0011-21-03 11:00

 

For information on the loading and unloading date fields, see Load and unload date fields in stops.

Freight orders 001, 002, and 003: Load plan 2 consolidation

For load plan 2, the load building engine creates the following stops and trips:

TripCarrierTransport means groupStandard route
000000000153Speedex Int BVTR1 Trucks 40m²OW-A-B

 

The carrier is selected because it is available according to its calendar and the calendar of the loading and unloading addresses, and because it matches the criteria of the Carrier/LSP Selection Criterion used for the load plan.

The transport means group is selected because it is attached to the selected carrier and because the properties of the transport means group and the items on the freight order lines, such as Combination Code or Transport Type, do not conflict. For further information on the Carrier/LSP Selection Criterion, see Freight Planning Parameters (fmlbd0100m000). In this example, a carrier and a transport means group was not entered on the freight orders or the freight order lines.

The standard route was selected because this route covers the load and unload addresses of the freight orders on which load plan 2 is based, and because it meets the Carrier/LSP Selection Criterion used for the load plan.

Note

Load plan 2, which is created using the consolidation planning method, has one trip, going from the Own warehouse to customer A and customer B, in which all the goods are transported using a single vehicle. Load plan 1, for which the direct shipping planning method is used, has two trips, the first going from the Own warehouse to customer A, and the second going from the Own warehouse to customer B, each trip using a separate vehicle.

For trip 000000000153, LN creates stop codes 100000000001 and 100000000002. Stop code 100000000001 has a load stop and an unload stop. Stop 100000000002 has an unloading stop.

Load planLoad plan 2
Trip000000000153
Stop code100000000001
Stop typeAddressMinimum load/unload dateMaximum load/unload dateOptimal date
LoadOwn warehouse11-21-03 07:0011-21-03 20:4011-21-03 09:32
UnloadCustomer A11-21-03 08:1911-21-03 22:0011-21-03 10:51

 

Load planLoad plan 2
Trip000000000153
Stop code100000000002
Stop typeAddressMinimum unload dateMaximum unload dateOptimal date
UnloadCustomer B11-21-03 08:4311-21-03 23:0011-21-03 11:15

 

For information on the loading and unloading date fields, see Load and unload date fields in stops.

Note

In LN, fractions of minutes are rounded down. For example, a travel time of 01:19:20 becomes 01:19. This conversion has a minor impact on planning calculations.

Freight orders 004 and 005: Load plan 3 pooling

For load plan 3, that includes freight orders 004 and 005, the load building engine creates one trip for each of the legs of the route plan selected for the load plan. Each trip has one stop, and each stop has a loading stop and an unloading stop.

The following table shows the freight order, route plan leg, and loading/unloading address that each trip covers.

TripFreight orderRoute plan leg typeLoading addressUnloading address
...154004AdvanceCustomer C, The Hague, NetherlandsRotterdam Sea Terminal
...155004 and 005MainRotterdam Sea TerminalSheerness Sea Terminal, UK
...156004BeyondSheerness Sea Terminal, UKCustomer C, Luton, UK
...157005AdvanceCustomer D, Amsterdam, NetherlandsRotterdam Sea Terminal
...158005BeyondSheerness Sea Terminal, UKCustomer D, Windsor, UK

 

The following tables show the most important stop and trip data. Full stop and trip details appear in the Stops (fmlbd1500m000) session and the Trips (fmlbd2500m000) session.

Load planLoad plan 3----
Route planCH-SE----
Stop code100000000001----
Stop typeLoad----
TripAddressMinimum load dateMaximum load dateOptimal dateRoute plan leg
...154Own warehouse, The Hague, Netherlands11-21-03 07:0011-21-03 22:0011-21-03 19:54Advance
...155Rotterdam Sea Terminal11-21-03 07:3911-22-03 04:2011-21-03 20:21Main
...156Sheerness Sea Terminal, UK11-21-03 19:1911-22-03 16:0011-22-03 08:01Advance

 

Load planLoad plan 3----
Route planCH-SE----
Stop code100000000001----
Stop typeUnload----
TripAddressMinimum unload dateMaximum unload dateOptimal dateRoute plan leg
...154Rotterdam Sea Terminal11-21-03 07:3911-22-03 04:2011-21-03 20:21Advance
...155Sheerness Sea Terminal, UK11-21-03 19:1911-22-03 16:0011-22-03 08:01Main
...156Customer C, Luton, UK11-22-03 08:0011-22-03 17:0011-22-03 09:01Beyond

 

Load planLoad plan 3----
Route planCH-SE----
Stop code100000000002----
Stop typeLoad----
TripAddressMinimum load dateMaximum load dateOptimal dateRoute plan leg
...157Amsterdam, Netherlands11-21-03 07:0011-21-03 21:0011-21-03 19:42Advance
...158Sheerness Sea Terminal, UK11-21-03 19:1911-22-03 16:0011-22-03 08:01Beyond

 

Load planLoad plan 3----
Route planCH-SE----
Stop code100000000002----
Stop typeUnload----
TripAddressMinimum unload dateMaximum unload dateOptimal dateRoute plan leg
...157Sheerness Sea Terminal, UK11-21-03 07:3911-22-03 04:2011-21-03 20:21Advance
...158Customer D, Windsor, UK11-22-03 08:0011-22-03 17:0011-22-03 08:58Beyond

 

For further information on the minimum and maximum loading and unloading date fields, see Load and unload date fields in stops.

Loads and shipments

The third step of the load building process is to create loads and shipments from the stops and trips created in the previous step.

Freight orders 001, 002, and 003: Load plan 1 direct shipping

For load plan 1, the load building engine creates the following loads and shipments:

LoadShipmentLoad addressUnload addressPlanned load datePlanned unload dateFreight orderFreight order line
LD0250SHP0105Own warehouseCustomer A21-11-03 09:4021-11-03 10:5900110
LD0250SHP0105Own warehouseCustomer A21-11-03 09:4021-11-03 10:5900310
LD0251SHP0106Own warehouseCustomer B21-11-03 09:3321-11-03 11:0000210

 

Freight orders 001 and 003 are combined and converted to shipment SHP0105, which is included in load LD0250. Freight order 002, which has a different destination, is converted to shipment SHP0106, which is included in load LD0251. These loads are transported separately, because these loads were planned by the direct shipping planning method.

Freight orders 001, 002, and 003: Load plan 2 consolidation

For load plan 2, the load building engine creates the following loads and shipments:

LoadShipmentLoad addressUnload addressPlanned load datePlanned unload dateFreight orderFreight order line
LD0252SHP0107Own warehouseCustomer A21-11-03 09:2021-11-03 10:3900110
LD0252SHP0108Own warehouseCustomer A21-11-03 09:2021-11-03 10:3900310
LD0252SHP0109Own warehouseCustomer B21-11-03 09:2021-11-03 11:3900210

 

The consolidation planning method combines shipments into loads whenever their transport routes overlap. In load plan 2, the loading address is the same for each shipment, and the unloading addresses are covered by the selected standard route. The shipments in this load plan travel the same standard route, therefore these shipments are consolidated in the same load.

Freight orders 004 and 005: Load plan 3, pooling

For load plan 3, the load building engine creates the following loads and shipments:

LoadShipmentLoad addressUnload addressPlanned load datePlanned unload dateFreight order/lineLeg type
LD0253SHP0110Own warehouseRotterdam Sea Terminal21-11-03 19:5421-11-03 20:21004/10Advance
LD0254SHP0111Rotterdam Sea TerminalSheerness Sea Terminal, UK21-11-03 20:2122-11-03 08:01004/10Main
LD0255SHP0112Sheerness Sea Terminal, UKCustomer C, Luton, UK21-11-03 09:2021-11-03 11:39004/10Beyond
LD0256SHP0113Supplier's warehouse, Amsterdam, NetherlandsRotterdam Sea Terminal21-11-03 19:4221-11-03 20:21005/10Advance
LD0254SHP0114Rotterdam Sea TerminalSheerness Sea Terminal, UK21-11-03 20:2122-11-03 08:01005/10Main
LD0257SHP0115Sheerness Sea Terminal, UKCustomer D, Windsor, UK22-11-03 08:0122-11-03 08:58005/10Beyond

 

For each advance and beyond leg of the route plan, a separate load is created because each of these legs cover a different route. Each of these loads has one shipment.

The main leg is the part of the transport route that all the goods travel together in one load (the cargo ship has more than sufficient loading capacity to carry all the goods), load LD0254. Load LD0254 carries two shipments, one shipment for each freight order of load plan 3. The Freight order/line column in the table shows in which loads and shipments the goods of the freight orders are transported.

The planned load dates equal the optimal dates of the load stops. The planned unload dates equal the optimal dates of the unload stops. An overview of the freight orders and freight order lines from which the loads and shipments of a plan are created is provided in the Freight Order Lines by Plan (fmlbd3150m100) session. Shipment details appear in the Shipments (fmlbd3100m000) and Shipment Lines (fmlbd3150m000) sessions, and load details appear in the Loads (fmlbd4100m000).