| 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 order | Ship-from address | Ship-to address |  | Load dates | Unload dates | Item
001 | Own warehouse | Customer A | Earliest | 11-21-03 07:00 | 11-21-03 08:00 | 100 monitors
Planned | 11-21-03 08:00 | 11-21-03 11:00
Latest | 11-21-03 22:00 | 11-21-03 22:00
002 | Own warehouse | Customer B | Earliest | 11-21-03 07:00 | 11-21-03 08:00 | 120 monitors
Planned | 11-21-03 08:00 | 11-21-03 11:00
Latest | 11-21-03 22:00 | 11-21-03 23:00
003 | Own warehouse | Customer A | Earliest | 11-21-03 07:00 | 11-21-03 08:00 | 100 keyboards
Planned | 11-21-03 08:00 | 11-21-03 11:00
Latest | 11-21-03 22:00 | 11-21-03 22:00
For freight orders 001, 002, and 003, the following carrier is available:
Carrier | Transport means group | Average speed
--- | --- | ---
Speedex Int Ltd | TR1-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 order | Ship-from address | Ship-to address | Load dates | Unload dates | Item
004 | Own warehouse, The Hague, The Netherlands | Customer C, Luton, United Kingdom | Earliest | 11-21-03 07:00 | 11-22-03 08:00 | 100 monitors
Planned | 11-21-03 08:00 | 11-22-03 09:00
Latest | 11-21-03 22:00 | 11-22-03 17:00
005 | Supplier's warehouse, Amsterdam, The Netherlands | Customer D, Windsor, United Kingdom | Earliest | 11-21-03 07:00 | 11-22-03 08:00 | 120 monitors
Planned | 11-21-03 08:00 | 11-22-03 09:00
Latest | 11-21-03 21:00 | 11-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 type | Origin address | Destination address | Distance
--- | --- | --- | ---
Advance | BGN00234 | The Hague, Netherlands | BGN04223 | Rotterdam Sea Terminal | 45 km
Advance | BGN00289 | Amsterdam, Netherlands | BGN04223 | Rotterdam Sea Terminal | 65 km
Main | BGN04223 | Rotterdam Sea Terminal | BGN82266 | Sheerness Sea Terminal, UK | 350 km
Beyond | BGN82266 | Sheerness Sea Terminal, UK | CGB20036 | Luton, UK | 100 km
Beyond | BGN82266 | Sheerness Sea Terminal, UK | CGB21458 | Windsor, UK | 95 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:
Carrier | Transport means group | Average speed
--- | --- | ---
Speedex Int BV | TR1-Trucks 40m² | 100 km/h
TransIt Ltd | TR1-Trucks 40m² | 100 km/h
Overseas Ltd | CV1- cargo ships | 30 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
From | To | Km | Travel time
--- | --- | --- | ---
Own warehouse | Customer A | 132 | 1 hour, 19 minutes
Customer A | Customer B | 40 | 24 minutes
Own warehouse | Customer B | 145 | 1 hour, 27 minutes
Own warehouse | Customer C | 495 | 13 hours, 7 minutes
Supplier's warehouse | Customer D | 510 | 13 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 order | Ship-from address | Ship-to address | Planned load date | Planned unload date | Combined freight order lines
--- | --- | --- | --- | --- | ---
Freight order/line | Item
100001 | Own warehouse | Customer A | 11-21-03 08:00 | 11-21-03 11:00 | 001/10 | 100 monitors
003/10 | 100 keyboards
100002 | Own warehouse | Customer B | 11-21-03 08:00 | 11-21-03 11:00 | 002/10 | 120 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 order | Ship-from address | Ship-to address | Planned load date | Planned unload date | Combined freight order lines
--- | --- | --- | --- | --- | ---
Freight order/line | Item
100001 | Own warehouse | Customer C | 11-21-03 08:00 | 11-22-03 09:00 | 004/10 | 100 monitors
100002 | Supplier's warehouse | Customer D | 11-21-03 08:00 | 11-22-03 09:00 | 005/10 | 120 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:
Trip | Carrier | Transport means group
--- | --- | ---
000000000150 | Speedex Int BV | TR1 Trucks 40m²
000000000151 | Speedex Int BV | TR1 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, ERP LN created stop code 100000000001. Stop code 100000000001 includes a load stop and an unload stop. For trip 000000000151, ERP 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 plan | Load plan 1 direct shipping
Stop code | 100000000001
Trip | 000000000150
Stop type | Address | Minimum load/unload date | Maximum load/unload date | Optimal date
--- | --- | --- | --- | ---
Load | Own warehouse | 11-21-03 07:00 | 11-21-03 20:40 | 11-21-03 09:40
Unload | Customer A | 11-21-03 08:19 | 11-21-03 22:00 | 11-21-03 10:59
Note In ERP 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 plan | Load plan 1 direct shipping
Stop code | 100000000002
Trip | 000000000151
Stop type | Address | Minimum load/unload date | Maximum load/unload date | Optimal date
--- | --- | --- | --- | ---
Load | Own warehouse | 11-21-03 07:00 | 11-21-03 21:33 | 11-21-03 09:33
Unload | Customer A | 11-21-03 08:27 | 11-21-03 23:00 | 11-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:
Trip | Carrier | Transport means group | Standard route
--- | --- | --- | ---
000000000153 | Speedex Int BV | TR1 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, ERP 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 plan | Load plan 2
Trip | 000000000153
Stop code | 100000000001
Stop type | Address | Minimum load/unload date | Maximum load/unload date | Optimal date
--- | --- | --- | --- | ---
Load | Own warehouse | 11-21-03 07:00 | 11-21-03 20:40 | 11-21-03 09:32
Unload | Customer A | 11-21-03 08:19 | 11-21-03 22:00 | 11-21-03 10:51
Load plan | Load plan 2
Trip | 000000000153
Stop code | 100000000002
Stop type | Address | Minimum unload date | Maximum unload date | Optimal date
--- | --- | --- | --- | ---
Unload | Customer B | 11-21-03 08:43 | 11-21-03 23:00 | 11-21-03 11:15
For information on the loading and unloading date fields, see Load and unload date fields in stops. Note In ERP 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.
Trip | Freight order | Route plan leg type | Loading address | Unloading address
--- | --- | --- | --- | ---
...154 | 004 | Advance | Customer C, The Hague, Netherlands | Rotterdam Sea Terminal
...155 | 004 and 005 | Main | Rotterdam Sea Terminal | Sheerness Sea Terminal, UK
...156 | 004 | Beyond | Sheerness Sea Terminal, UK | Customer C, Luton, UK
...157 | 005 | Advance | Customer D, Amsterdam, Netherlands | Rotterdam Sea Terminal
...158 | 005 | Beyond | Sheerness Sea Terminal, UK | Customer 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 plan | Load plan 3 | - | - | - | -
Route plan | CH-SE | - | - | - | -
Stop code | 100000000001 | - | - | - | -
Stop type | Load | - | - | - | -
Trip | Address | Minimum load date | Maximum load date | Optimal date | Route plan leg
--- | --- | --- | --- | --- | ---
...154 | Own warehouse, The Hague, Netherlands | 11-21-03 07:00 | 11-21-03 22:00 | 11-21-03 19:54 | Advance
...155 | Rotterdam Sea Terminal | 11-21-03 07:39 | 11-22-03 04:20 | 11-21-03 20:21 | Main
...156 | Sheerness Sea Terminal, UK | 11-21-03 19:19 | 11-22-03 16:00 | 11-22-03 08:01 | Advance
Load plan | Load plan 3 | - | - | - | -
Route plan | CH-SE | - | - | - | -
Stop code | 100000000001 | - | - | - | -
Stop type | Unload | - | - | - | -
Trip | Address | Minimum unload date | Maximum unload date | Optimal date | Route plan leg
--- | --- | --- | --- | --- | ---
...154 | Rotterdam Sea Terminal | 11-21-03 07:39 | 11-22-03 04:20 | 11-21-03 20:21 | Advance
...155 | Sheerness Sea Terminal, UK | 11-21-03 19:19 | 11-22-03 16:00 | 11-22-03 08:01 | Main
...156 | Customer C, Luton, UK | 11-22-03 08:00 | 11-22-03 17:00 | 11-22-03 09:01 | Beyond
Load plan | Load plan 3 | - | - | - | -
Route plan | CH-SE | - | - | - | -
Stop code | 100000000002 | - | - | - | -
Stop type | Load | - | - | - | -
Trip | Address | Minimum load date | Maximum load date | Optimal date | Route plan leg
--- | --- | --- | --- | --- | ---
...157 | Amsterdam, Netherlands | 11-21-03 07:00 | 11-21-03 21:00 | 11-21-03 19:42 | Advance
...158 | Sheerness Sea Terminal, UK | 11-21-03 19:19 | 11-22-03 16:00 | 11-22-03 08:01 | Beyond
Load plan | Load plan 3 | - | - | - | -
Route plan | CH-SE | - | - | - | -
Stop code | 100000000002 | - | - | - | -
Stop type | Unload | - | - | - | -
Trip | Address | Minimum unload date | Maximum unload date | Optimal date | Route plan leg
--- | --- | --- | --- | --- | ---
...157 | Sheerness Sea Terminal, UK | 11-21-03 07:39 | 11-22-03 04:20 | 11-21-03 20:21 | Advance
...158 | Customer D, Windsor, UK | 11-22-03 08:00 | 11-22-03 17:00 | 11-22-03 08:58 | Beyond
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:
Load | Shipment | Load address | Unload address | Planned load date | Planned unload date | Freight order | Freight order line
--- | --- | --- | --- | --- | --- | --- | ---
LD0250 | SHP0105 | Own warehouse | Customer A | 21-11-03 09:40 | 21-11-03 10:59 | 001 | 10
LD0250 | SHP0105 | Own warehouse | Customer A | 21-11-03 09:40 | 21-11-03 10:59 | 003 | 10
LD0251 | SHP0106 | Own warehouse | Customer B | 21-11-03 09:33 | 21-11-03 11:00 | 002 | 10
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:
Load | Shipment | Load address | Unload address | Planned load date | Planned unload date | Freight order | Freight order line
--- | --- | --- | --- | --- | --- | --- | ---
LD0252 | SHP0107 | Own warehouse | Customer A | 21-11-03 09:20 | 21-11-03 10:39 | 001 | 10
LD0252 | SHP0108 | Own warehouse | Customer A | 21-11-03 09:20 | 21-11-03 10:39 | 003 | 10
LD0252 | SHP0109 | Own warehouse | Customer B | 21-11-03 09:20 | 21-11-03 11:39 | 002 | 10
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:
Load | Shipment | Load address | Unload address | Planned load date | Planned unload date | Freight order/line | Leg type
--- | --- | --- | --- | --- | --- | --- | ---
LD0253 | SHP0110 | Own warehouse | Rotterdam Sea Terminal | 21-11-03 19:54 | 21-11-03 20:21 | 004/10 | Advance
LD0254 | SHP0111 | Rotterdam Sea Terminal | Sheerness Sea Terminal, UK | 21-11-03 20:21 | 22-11-03 08:01 | 004/10 | Main
LD0255 | SHP0112 | Sheerness Sea Terminal, UK | Customer C, Luton, UK | 21-11-03 09:20 | 21-11-03 11:39 | 004/10 | Beyond
LD0256 | SHP0113 | Supplier's warehouse, Amsterdam, Netherlands | Rotterdam Sea Terminal | 21-11-03 19:42 | 21-11-03 20:21 | 005/10 | Advance
LD0254 | SHP0114 | Rotterdam Sea Terminal | Sheerness Sea Terminal, UK | 21-11-03 20:21 | 22-11-03 08:01 | 005/10 | Main
LD0257 | SHP0115 | Sheerness Sea Terminal, UK | Customer D, Windsor, UK | 22-11-03 08:01 | 22-11-03 08:58 | 005/10 | Beyond
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). Related topics Planning methods Examples of the use of the planned date determiner options To create load plans Load and unload date fields in stops |