Dock Door Constraints (Transportation Optimization)

Without dock door constraints, the transportation optimization engine (Hopper) assumes facilities and customers can load and unload any number of vehicles at the same time. In reality, a depot with 2 dock doors can only service 2 vehicles at once, and routes that look good on paper may be impossible to execute. Dock door constraints let you model that limit, so the routes and schedules Hopper produces are operationally realistic.

Example business questions that can be answered with the help of dock door constraints:

  • Are my planned routes actually feasible given the number of dock doors at my depots and customers?
  • Where in my network (depots and customers) are dock doors the bottleneck, and what does it cost me in wait time or extra routes?
  • How many dock doors does a depot need to avoid delays?
  • What is the impact of a depot temporarily running with fewer doors due to maintenance or construction?
  • If I add a depot or shift volume, how do dock limits change the picture?
  • How do customers’ limited dock doors affect my route timing and the number of vehicles I need?

Please note that a basic knowledge of Hopper prior to diving into this content is recommended, see the Getting Started with Hopper article.

How to Set Dock Door Constraints

Dock door constraints are specified by using the new Number of Dock Doors column on the Facilities and Customers tables. The new field on the Facilities table is shown here:

If Number of Dock Doors is:

  • Left blank (default) – there is no limit on how many assets can be loading/unloading at the facility/customer simultaneously.
  • Set to a positive integer – this is the maximum number of assets that can be loading/unloading at the facility/customer simultaneously.

How Dock Door Constraints Work

Dock doors can be occupied by assets (vehicles/trucks) which are loading and/or unloading.

The time an asset spends (un)loading at a dock door is determined by pickup and delivery times that can be specified in following input tables: Customers, Facilities, Transportation Assets, and Shipments. Fixed and variable (“unit”) pickup and delivery times plus their units of measure can be specified on all tables, and these times are additive.

Heads up

Note that if no delivery or pickup times are specified at a facility or customer, loading and unloading are instantaneous and applying any dock door constraints will not result in outputs changing.

‍

Assets do not occupy a dock door when they are waiting.

If used, business hours and business calendars need to be satisfied as with any other Hopper runs, while the Complete Service in Time Window run setting also impacts when service at a facility can start and end.

If due to a dock door constraint, a shipment cannot be routed like it otherwise would, Hopper will take the usual steps of changing the timing of stops/routes, moving stops around, trying shipments on different routes, using more assets or a different asset mix, etc. Ultimately, it is possible that dock door constraints make it such that one or multiple shipments cannot be routed, which will be indicated with Shipment Status = Unrouted in the Transportation Shipment Summary output table.

Dock Door Constraints Example

We will use an example that is set up on a copy of a model from the Resource Library: Multi Stop Routes with Time Windows. You can copy it to your own account if you want to follow along. In this model there are 2 depots, one in Atlanta and one in Jacksonville, from which product is picked up and then delivered to 31 customers in Georgia. Several scenarios that explore routes, fleet mix, use of the second depot, and integration of a new customer base consisting of 13 customers into the existing one are already set up.

In our relatively simple example, we will update an existing scenario by specifying that the Atlanta Depot only has 1 dock door available. Then we run the original scenario without any dock door constraints together with the updated scenario and compare the outputs.

In the Scenarios module of this model:

  1. We use scenario 6_Alt Source_Combined Markets as the original scenario without dock door constraints.
  2. The scenario is duplicated and named 6_Alt Source_Combined Markets ATL 1 Dock Door. It has the same 4 scenario items as the original scenario, and 1 new item, Set Dock Doors 1 ATL. In this item:
    1. Table Name – set to Facilities, the change is made on this table.
    2. Actions – set to numberofdockdoors = ‘1’, this overwrites the current blank value of the Number of Dock Doors field with a 1.
    3. Conditions – facilityname = ‘ATLANTA DEPOT’, only the record for the Atlanta Depot is updated; the other record in the Facilities table for JACKSONVILLE DEPOT will have the Number of Dock Doors field left blank.

After running both scenarios with the Solver Focus run setting set to High Precision, we filter the Transportation Stop Summary output table for the 2 scenarios we ran, ATLANTA DEPOT as the Site Name, and Stop Type = Pickup. We see that for loading that occurs at Atlanta, these 2 scenarios differ on one date, 2024-04-03:

  1. In the 6_Alt Source_Combined Markets scenario 2 assets are being loaded for 2 different routes. They have some overlap: between 08:22:11 and 08:34:48 both trucks are being serviced.
  2. When adding the requirement that only 1 asset can be loaded/unloaded at a time at Atlanta in the 6_Alt Source_Combined Markets ATL 1 Dock Door scenario, we see there is no more overlap on this date: the trucks are now loaded sequentially, where the second starts loading when the first one is done loading at 08:37:12.

If you review the Transportation Summary output table you will find these 2 scenarios have the exact same cost, transport distances, and transport, break, and rest times. The only difference is that one route’s timing has shifted. Without the constraint, Hopper would have loaded two trucks at once, which is impossible at the Atlanta Depot with a single dock door. So, even though the cost is unchanged, the schedule is now feasible.

‍

As always, please do not hesitate to contact our Support team on support@optilogic.com in case of any questions or feedback.

Without dock door constraints, the transportation optimization engine (Hopper) assumes facilities and customers can load and unload any number of vehicles at the same time. In reality, a depot with 2 dock doors can only service 2 vehicles at once, and routes that look good on paper may be impossible to execute. Dock door constraints let you model that limit, so the routes and schedules Hopper produces are operationally realistic.

Example business questions that can be answered with the help of dock door constraints:

  • Are my planned routes actually feasible given the number of dock doors at my depots and customers?
  • Where in my network (depots and customers) are dock doors the bottleneck, and what does it cost me in wait time or extra routes?
  • How many dock doors does a depot need to avoid delays?
  • What is the impact of a depot temporarily running with fewer doors due to maintenance or construction?
  • If I add a depot or shift volume, how do dock limits change the picture?
  • How do customers’ limited dock doors affect my route timing and the number of vehicles I need?

Please note that a basic knowledge of Hopper prior to diving into this content is recommended, see the Getting Started with Hopper article.

How to Set Dock Door Constraints

Dock door constraints are specified by using the new Number of Dock Doors column on the Facilities and Customers tables. The new field on the Facilities table is shown here:

If Number of Dock Doors is:

  • Left blank (default) – there is no limit on how many assets can be loading/unloading at the facility/customer simultaneously.
  • Set to a positive integer – this is the maximum number of assets that can be loading/unloading at the facility/customer simultaneously.

How Dock Door Constraints Work

Dock doors can be occupied by assets (vehicles/trucks) which are loading and/or unloading.

The time an asset spends (un)loading at a dock door is determined by pickup and delivery times that can be specified in following input tables: Customers, Facilities, Transportation Assets, and Shipments. Fixed and variable (“unit”) pickup and delivery times plus their units of measure can be specified on all tables, and these times are additive.

Heads up

Note that if no delivery or pickup times are specified at a facility or customer, loading and unloading are instantaneous and applying any dock door constraints will not result in outputs changing.

‍

Assets do not occupy a dock door when they are waiting.

If used, business hours and business calendars need to be satisfied as with any other Hopper runs, while the Complete Service in Time Window run setting also impacts when service at a facility can start and end.

If due to a dock door constraint, a shipment cannot be routed like it otherwise would, Hopper will take the usual steps of changing the timing of stops/routes, moving stops around, trying shipments on different routes, using more assets or a different asset mix, etc. Ultimately, it is possible that dock door constraints make it such that one or multiple shipments cannot be routed, which will be indicated with Shipment Status = Unrouted in the Transportation Shipment Summary output table.

Dock Door Constraints Example

We will use an example that is set up on a copy of a model from the Resource Library: Multi Stop Routes with Time Windows. You can copy it to your own account if you want to follow along. In this model there are 2 depots, one in Atlanta and one in Jacksonville, from which product is picked up and then delivered to 31 customers in Georgia. Several scenarios that explore routes, fleet mix, use of the second depot, and integration of a new customer base consisting of 13 customers into the existing one are already set up.

In our relatively simple example, we will update an existing scenario by specifying that the Atlanta Depot only has 1 dock door available. Then we run the original scenario without any dock door constraints together with the updated scenario and compare the outputs.

In the Scenarios module of this model:

  1. We use scenario 6_Alt Source_Combined Markets as the original scenario without dock door constraints.
  2. The scenario is duplicated and named 6_Alt Source_Combined Markets ATL 1 Dock Door. It has the same 4 scenario items as the original scenario, and 1 new item, Set Dock Doors 1 ATL. In this item:
    1. Table Name – set to Facilities, the change is made on this table.
    2. Actions – set to numberofdockdoors = ‘1’, this overwrites the current blank value of the Number of Dock Doors field with a 1.
    3. Conditions – facilityname = ‘ATLANTA DEPOT’, only the record for the Atlanta Depot is updated; the other record in the Facilities table for JACKSONVILLE DEPOT will have the Number of Dock Doors field left blank.

After running both scenarios with the Solver Focus run setting set to High Precision, we filter the Transportation Stop Summary output table for the 2 scenarios we ran, ATLANTA DEPOT as the Site Name, and Stop Type = Pickup. We see that for loading that occurs at Atlanta, these 2 scenarios differ on one date, 2024-04-03:

  1. In the 6_Alt Source_Combined Markets scenario 2 assets are being loaded for 2 different routes. They have some overlap: between 08:22:11 and 08:34:48 both trucks are being serviced.
  2. When adding the requirement that only 1 asset can be loaded/unloaded at a time at Atlanta in the 6_Alt Source_Combined Markets ATL 1 Dock Door scenario, we see there is no more overlap on this date: the trucks are now loaded sequentially, where the second starts loading when the first one is done loading at 08:37:12.

If you review the Transportation Summary output table you will find these 2 scenarios have the exact same cost, transport distances, and transport, break, and rest times. The only difference is that one route’s timing has shifted. Without the constraint, Hopper would have loaded two trucks at once, which is impossible at the Atlanta Depot with a single dock door. So, even though the cost is unchanged, the schedule is now feasible.

‍

As always, please do not hesitate to contact our Support team on support@optilogic.com in case of any questions or feedback.

Have More Questions?

Contact Support

Get in touch

Contact Sales

Get in touch

Visit Frogger Pond Community

Visit our Community