Examples of the execution of the load building process

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:

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

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:

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

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:

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:

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

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:

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.

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

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.

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

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

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.

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

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

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.

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.

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

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.

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.

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

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

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

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.

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

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.

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

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).