vrp_vroomShipmentsPlain - Experimental

vrp_vroomShipmentsPlain - Vehicle Routing Problem with VROOM, involving only shipments, with plain integer values instead of TIMESTAMP or INTERVAL.

Warning

Possible server crash

  • These functions might create a server crash

Warning

Experimental functions

  • They are not officially of the current release.

  • They likely will not be officially be part of the next release:

    • The functions might not make use of ANY-INTEGER and ANY-NUMERICAL

    • Name might change.

    • Signature might change.

    • Functionality might change.

    • pgTap tests might be missing.

    • Might need c/c++ coding.

    • May lack documentation.

    • Documentation if any might need to be rewritten.

    • Documentation examples might need to be automatically generated.

    • Might need a lot of feedback from the comunity.

    • Might depend on a proposed function of vrpRouting

    • Might depend on a deprecated function of vrpRouting

Availability

Version 0.3.0

  • Function modified for VROOM 1.11.0

Version 0.2.0

  • New experimental function

Description

VROOM is an open-source optimization engine that aims at providing good solutions to various real-life vehicle routing problems (VRP) within a small computing time. This function can be used to get the solution to a problem involving only shipments.

Signature

vrp_vroomShipmentsPlain(
[, exploration_level] [, timeout]) – Experimental on v0.2
RETURNS SET OF
(seq, vehicle_seq, vehicle_id, vehicle_data, step_seq, step_type, task_id,
task_data, arrival, travel_time, service_time, waiting_time, departure, load)

Example: This example is based on the VROOM Data of the Sample Data network:

SELECT *
FROM vrp_vroomShipmentsPlain(
  'SELECT * FROM vroom.shipments',
  'SELECT * FROM vroom.shipments_time_windows',
  'SELECT * FROM vroom.vehicles',
  'SELECT * FROM vroom.breaks',
  'SELECT * FROM vroom.breaks_time_windows',
  'SELECT * FROM vroom.matrix'
);
 seq | vehicle_seq | vehicle_id | vehicle_data | step_seq | step_type | task_id | location_id | task_data | arrival | travel_time | setup_time | service_time | waiting_time | departure | load
-----+-------------+------------+--------------+----------+-----------+---------+-------------+-----------+---------+-------------+------------+--------------+--------------+-----------+------
   1 |           1 |          1 | {}           |        1 |         1 |      -1 |           1 | {}        |     300 |           0 |          0 |            0 |            0 |       300 | {0}
   2 |           1 |          1 | {}           |        2 |         5 |       1 |           1 | {}        |     300 |           0 |          0 |            0 |            0 |       300 | {0}
   3 |           1 |          1 | {}           |        3 |         3 |       4 |           1 | {}        |     300 |           0 |          0 |         2250 |         6075 |      8625 | {20}
   4 |           1 |          1 | {}           |        4 |         4 |       4 |           4 | {}        |    8700 |          75 |          0 |         2250 |          225 |     11175 | {0}
   5 |           1 |          1 | {}           |        5 |         3 |       5 |           2 | {}        |   11265 |          90 |          0 |         2250 |         2085 |     15600 | {10}
   6 |           1 |          1 | {}           |        6 |         3 |       3 |           1 | {}        |   15650 |          50 |          0 |         2250 |            0 |     17900 | {30}
   7 |           1 |          1 | {}           |        7 |         4 |       5 |           2 | {}        |   17950 |          50 |          0 |         2250 |          225 |     20425 | {20}
   8 |           1 |          1 | {}           |        8 |         4 |       3 |           2 | {}        |   20425 |           0 |          0 |         2250 |          200 |     22875 | {0}
   9 |           1 |          1 | {}           |        9 |         6 |      -1 |           1 | {}        |   22925 |          50 |          0 |            0 |            0 |     22925 | {0}
  10 |           1 |          1 | {}           |        0 |         0 |       0 |           0 | {}        |       0 |         315 |          0 |        13500 |         8810 |         0 | {}
  11 |           2 |          4 | {}           |        1 |         1 |      -1 |           3 | {}        |     250 |           0 |          0 |            0 |            0 |       250 | {0}
  12 |           2 |          4 | {}           |        2 |         5 |       4 |           1 | {}        |     250 |           0 |          0 |            0 |            0 |       250 | {0}
  13 |           2 |          4 | {}           |        3 |         3 |       2 |           5 | {}        |     275 |          25 |          0 |         2250 |          100 |      2625 | {10}
  14 |           2 |          4 | {}           |        4 |         3 |       1 |           3 | {}        |    2650 |          25 |          0 |         2250 |            0 |      4900 | {20}
  15 |           2 |          4 | {}           |        5 |         4 |       2 |           6 | {}        |    4990 |          90 |          0 |         2250 |            0 |      7240 | {10}
  16 |           2 |          4 | {}           |        6 |         4 |       1 |           5 | {}        |    7351 |         111 |          0 |         2250 |        17574 |     27175 | {0}
  17 |           2 |          4 | {}           |        7 |         6 |      -1 |           3 | {}        |   27200 |          25 |          0 |            0 |            0 |     27200 | {0}
  18 |           2 |          4 | {}           |        0 |         0 |       0 |           0 | {}        |       0 |         276 |          0 |         9000 |        17674 |         0 | {}
  19 |           0 |          0 | {}           |        0 |         0 |       0 |           0 | {}        |       0 |         591 |          0 |        22500 |        26484 |         0 | {}
(19 rows)

Parameters

Parameter

Type

Description

Shipments SQL

TEXT

Query describing pickup and delivery tasks that should happen within same route.

Shipments Time Windows SQL

TEXT

Query describing valid slots for pickup and delivery service start.

Vehicles SQL

TEXT

Query describing the available vehicles.

Breaks SQL

TEXT

Query describing the driver breaks.

Breaks Time Windows SQL

TEXT

Query describing valid slots for break start.

Time Matrix SQL

TEXT

Query containing the distance or travel times between the locations.

Optional Parameters

Parameter

Type

Default

Description

exploration_level

INTEGER

\(5\)

Exploration level to use while solving.

  • Ranges from [0, 5]

  • A smaller exploration level gives faster result.

timeout

INTEGER

\(-1\)

Timeout value to stop the solving process.

  • Gives the best possible solution within a time limit. Note that some additional seconds may be required to return back the data.

  • Any negative timeout value is ignored.

Inner Queries

Shipments SQL

A SELECT statement that returns the following columns:

id
p_location_id, [p_setup, p_service, p_data]
d_location_id, [d_setup, d_service, d_data]
[amount, skills, priority]

Maximum values apply from vroom

p_setup, p_service, d_setup, d_service

  • \(4294967295\)

skills

  • \(2147483647\)

priority

  • \(100\)

Column

Type

Default

Description

id

ANY-INTEGER

Positive unique identifier of the shipment.

p_location_id

ANY-INTEGER

Positive unique identifier of the pickup location.

p_setup

ANY-INTEGER

\(0\)

The pickup setup duration

p_service

ANY-INTEGER

\(0\)

The pickup service duration

p_data

JSONB

'{}'::JSONB

Any metadata information of the pickup.

d_location_id

ANY-INTEGER

Positive unique identifier of the pickup location.

d_setup

ANY-INTEGER

\(0\)

The pickup setup duration

d_service

ANY-INTEGER

\(0\)

The pickup service duration

d_data

JSONB

'{}'::JSONB

Any metadata information of the delivery.

amount

ARRAY[ANY-INTEGER]

[]

Array of non-negative integers describing multidimensional quantities such as number of items, weight, volume etc.

  • All shipments must have the same value of array_length(amount, 1)

skills

ARRAY[ANY-INTEGER]

[]

Array of non-negative integers defining mandatory skills.

  • \(values \leq 2147483647\)

priority

INTEGER

\(0\)

Value range: \([0, 100]\)

Shipments Time Windows SQL

A SELECT statement that returns the following columns:

id, tw_open, tw_close
[kind]

Column

Type

Description

id

ANY-INTEGER

Positive unique identifier of the: job, pickup/delivery shipment, or break.

tw_open

ANY-INTEGER

Time window opening time.

tw_close

ANY-INTEGER

Time window closing time.

kind

CHAR

Value in [‘p’, ‘d’] indicating whether the time window is for:

  • Pickup shipment, or

  • Delivery shipment.

Vehicles SQL

A SELECT statement that returns the following columns:

id, start_id, end_id
[capacity, skills, tw_open, tw_close, speed_factor, max_tasks, data]

Maximum values apply from vroom

skills

  • \(2147483647\)

priority

  • \(100\)

Column

Type

Default

Description

id

ANY-INTEGER

Positive unique identifier of the vehicle.

start_id

ANY-INTEGER

Positive unique identifier of the start location.

end_id

ANY-INTEGER

Positive unique identifier of the end location.

capacity

ARRAY[ANY-INTEGER]

[]

Array of non-negative integers describing multidimensional quantities such as number of items, weight, volume etc.

  • All vehicles must have the same value of array_length(capacity, 1)

skills

ARRAY[ANY-INTEGER]

[]

Array of non-negative integers defining mandatory skills.

tw_open

ANY-INTEGER

\(0\)

Time window opening time.

  • tw_open leq tw_close

tw_close

ANY-INTEGER

\(4294967295\)

Time window closing time.

  • tw_open leq tw_close

speed_factor

ANY-NUMERICAL

\(1.0\)

Vehicle travel time multiplier.

  • Max value of speed factor for a vehicle shall not be greater than 5 times the speed factor of any other vehicle.

max_tasks

INTEGER

\(2147483647\)

Maximum number of tasks in a route for the vehicle.

  • A job, pickup, or delivery is counted as a single task.

data

JSONB

'{}'::JSONB

Any metadata information of the vehicle.

Note:

  • At least one of the start_id or end_id shall be present.

  • If end_id is omitted, the resulting route will stop at the last visited task, whose choice is determined by the optimization process.

  • If start_id is omitted, the resulting route will start at the first visited task, whose choice is determined by the optimization process.

  • To request a round trip, specify both start_id and end_id as the same index.

  • A vehicle is only allowed to serve a set of tasks if the resulting load at each route step is lower than the matching value in capacity for each metric. When using multiple components for amounts, it is recommended to put the most important/limiting metrics first.

  • It is assumed that all delivery-related amounts for jobs are loaded at vehicle start, while all pickup-related amounts for jobs are brought back at vehicle end.

Breaks SQL

A SELECT statement that returns the following columns:

id, vehicle_id
[service, data]

Column

Type

Default

Description

id

ANY-INTEGER

Positive unique identifier of the break. Unique for the same vehicle.

vehicle_id

ANY-INTEGER

Positive unique identifier of the vehicle.

service

ANY-INTEGER

\(0\)

The break duration

data

JSONB

'{}'::JSONB

Any metadata information of the break.

Breaks Time Windows SQL

A SELECT statement that returns the following columns:

id, tw_open, tw_close

Column

Type

Description

id

ANY-INTEGER

Positive unique identifier of the: job, pickup/delivery shipment, or break.

tw_open

ANY-INTEGER

Time window opening time.

tw_close

ANY-INTEGER

Time window closing time.

Time Matrix SQL

A SELECT statement that returns the following columns:

start_id, end_id, duration
[ cost]

Column

Type

Default

Description

start_id

ANY-INTEGER

Identifier of the start node.

end_id

ANY-INTEGER

Identifier of the end node.

duration

ANY-INTEGER

Time to travel from start_id to end_id

cost

ANY-INTEGER

duration

Cost of travel from start_id to end_id

Result Columns

Returns set of

(seq, vehicle_seq, vehicle_id, vehicle_data, step_seq, step_type, task_id,
 task_data, arrival, travel_time, service_time, waiting_time, load)

Column

Type

Description

seq

BIGINT

Sequential value starting from 1.

vehicle_seq

BIGINT

Sequential value starting from 1 for current vehicles. The \(n^{th}\) vehicle in the solution.

vehicle_id

BIGINT

Current vehicle identifier.

  • -1: Vehicle denoting all the unallocated tasks.

  • 0: Summary row for the complete problem

vehicle_data

JSONB

Metadata information of the vehicle.

step_seq

BIGINT

Sequential value starting from 1 for the stops made by the current vehicle. The \(m^{th}\) stop of the current vehicle.

  • 0: Summary row

step_type

BIGINT

Kind of the step location the vehicle is at:

  • 0: Summary row

  • 1: Starting location

  • 2: Job location

  • 3: Pickup location

  • 4: Delivery location

  • 5: Break location

  • 6: Ending location

task_id

BIGINT

Identifier of the task performed at this step.

  • 0: Summary row

  • -1: If the step is starting/ending location.

location_id

BIGINT

Identifier of the task location.

  • 0: Summary row

task_data

JSONB

Metadata information of the task.

arrival

ANY-INTEGER

Estimated time of arrival at this step.

travel_time

ANY-INTEGER

Travel time from previous step_seq to current step_seq.

  • 0: When step_type = 1

setup_time

ANY-INTEGER

Setup time at this step.

service_time

ANY-INTEGER

Service time at this step.

waiting_time

ANY-INTEGER

Waiting time at this step.

departure

ANY-INTEGER

Estimated time of departure at this step.

  • \(arrival + service\_time + waiting\_time\).

load

BIGINT

Vehicle load after step completion (with capacity constraints)

Note:

  • Unallocated tasks are mentioned at the end with vehicle_id = -1.

  • The last step of every vehicle denotes the summary row, where the columns travel_time, service_time and waiting_time denote the total time for the corresponding vehicle,

  • The last row denotes the summary for the complete problem, where the columns travel_time, service_time and waiting_time denote the total time for the complete problem,

Additional Example

Problem involving 1 shipment, using a single vehicle, similar to the VROOM Documentation Example 2 without jobs and with a shipment.

SELECT *
FROM vrp_vroomShipmentsPlain(
  $shipments$
    SELECT * FROM (
      VALUES (100, 1, 4)
    ) AS C(id, p_location_id, d_location_id)
  $shipments$,
  NULL,
  $vehicles$
    SELECT * FROM (
      VALUES (1, 1, 4)
    ) AS C(id, start_id, end_id)
  $vehicles$,
  NULL,
  NULL,
  $matrix$
    SELECT * FROM (
      VALUES (1, 2, 2104), (1, 3, 197), (1, 4, 1299),
             (2, 1, 2103), (2, 3, 2255), (2, 4, 3152),
             (3, 1, 197), (3, 2, 2256), (3, 4, 1102),
             (4, 1, 1299), (4, 2, 3153), (4, 3, 1102)
    ) AS C(start_id, end_id, duration)
  $matrix$
);
 seq | vehicle_seq | vehicle_id | vehicle_data | step_seq | step_type | task_id | location_id | task_data | arrival | travel_time | setup_time | service_time | waiting_time | departure | load
-----+-------------+------------+--------------+----------+-----------+---------+-------------+-----------+---------+-------------+------------+--------------+--------------+-----------+------
   1 |           1 |          1 | {}           |        1 |         1 |      -1 |           1 | {}        |       0 |           0 |          0 |            0 |            0 |         0 | {}
   2 |           1 |          1 | {}           |        2 |         3 |     100 |           1 | {}        |       0 |           0 |          0 |            0 |            0 |         0 | {}
   3 |           1 |          1 | {}           |        3 |         4 |     100 |           4 | {}        |    1299 |        1299 |          0 |            0 |            0 |      1299 | {}
   4 |           1 |          1 | {}           |        4 |         6 |      -1 |           4 | {}        |    1299 |           0 |          0 |            0 |            0 |      1299 | {}
   5 |           1 |          1 | {}           |        0 |         0 |       0 |           0 | {}        |       0 |        1299 |          0 |            0 |            0 |         0 | {}
   6 |           0 |          0 | {}           |        0 |         0 |       0 |           0 | {}        |       0 |        1299 |          0 |            0 |            0 |         0 | {}
(6 rows)

See Also

Indices and tables