本指南演示了路线优化解决方案中提供的车辆数量如何因请求参数而异。
Route Optimization API 不仅能优化装运完成订单，还会将这些装运分配给车辆，以便在您管理的限制下优化费用。
在第一个示例中，车辆数量与装运数量一致，并且所有车辆共享相同的费用和位置属性。每辆车都有每小时工时费用和每行驶公里费用，这有助于最大限度地缩短行程时间和距离。可能预期为多辆车分配运单，但示例响应显示的是，根据指定的成本模型参数，成本最低的解决方案。
查看包含多辆车的请求示例
{
"model": {
"globalStartTime": "2023-01-13T16:00:00-08:00",
"globalEndTime": "2023-01-14T16:00:00-08:00",
"shipments": [
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.789456,
"longitude": -122.390192
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 100.0
},
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.789116,
"longitude": -122.395080
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 5.0
},
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.795242,
"longitude": -122.399347
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 50.0
}
],
"vehicles": [
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerHour": 50.0,
"costPerKilometer": 10.0
},
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerHour": 50.0,
"costPerKilometer": 10.0
},
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerHour": 50.0,
"costPerKilometer": 10.0
}
]
}
}
查看对请求的响应（包含多辆车）
{
"routes": [
{
"vehicleStartTime": "2023-01-14T00:00:00Z",
"vehicleEndTime": "2023-01-14T00:28:22Z",
"visits": [
{
"isPickup": true,
"startTime": "2023-01-14T00:00:00Z",
"detour": "0s"
},
{
"shipmentIndex": 2,
"isPickup": true,
"startTime": "2023-01-14T00:02:30Z",
"detour": "150s"
},
{
"startTime": "2023-01-14T00:08:55Z",
"detour": "150s"
},
{
"shipmentIndex": 2,
"startTime": "2023-01-14T00:21:21Z",
"detour": "572s"
}
],
"transitions": [
{
"travelDuration": "0s",
"waitDuration": "0s",
"totalDuration": "0s",
"startTime": "2023-01-14T00:00:00Z"
},
{
"travelDuration": "0s",
"waitDuration": "0s",
"totalDuration": "0s",
"startTime": "2023-01-14T00:02:30Z"
},
{
"travelDuration": "235s",
"travelDistanceMeters": 795,
"waitDuration": "0s",
"totalDuration": "235s",
"startTime": "2023-01-14T00:05:00Z"
},
{
"travelDuration": "496s",
"travelDistanceMeters": 1893,
"waitDuration": "0s",
"totalDuration": "496s",
"startTime": "2023-01-14T00:13:05Z"
},
{
"travelDuration": "171s",
"travelDistanceMeters": 665,
"waitDuration": "0s",
"totalDuration": "171s",
"startTime": "2023-01-14T00:25:31Z"
}
],
"metrics": {
"performedShipmentCount": 2,
"travelDuration": "902s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "800s",
"totalDuration": "1702s",
"travelDistanceMeters": 3353
},
"routeCosts": {
"model.vehicles.cost_per_kilometer": 33.53,
"model.vehicles.cost_per_hour": 23.638888888888889
},
"routeTotalCost": 57.168888888888887
},
{
"vehicleIndex": 1
},
{
"vehicleIndex": 2
}
],
"skippedShipments": [
{
"index": 1
}
],
"metrics": {
"aggregatedRouteMetrics": {
"performedShipmentCount": 2,
"travelDuration": "902s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "800s",
"totalDuration": "1702s",
"travelDistanceMeters": 3353
},
"usedVehicleCount": 1,
"earliestVehicleStartTime": "2023-01-14T00:00:00Z",
"latestVehicleEndTime": "2023-01-14T00:28:22Z",
"totalCost": 62.168888888888887,
"costs": {
"model.vehicles.cost_per_hour": 23.638888888888889,
"model.shipments.penalty_cost": 5,
"model.vehicles.cost_per_kilometer": 33.53
}
}
}
求解器会将所有运单仅分配给一辆车，尽管有充足的车辆，但会跳过一次。这是因为附加车辆的运营费用太高，令人担忧，而且考虑到罚款费用较低，任何车辆都不具备成本效益来完成跳过的装运。尽管有车辆容量可用，但一辆车能以最经济高效的方式执行所有分配的装运。请求中的车辆未设置 usedIfRouteIsEmpty 属性（如需了解详情，请参阅 Vehicle 消息文档（REST、gRPC），因此若不使用，它们不会产生任何费用。
更改费用参数以优先优先采用全球范围更短的解决方案，而不是优先采用单条较短的车辆路线，从而导致更多车辆参与解决方案。下一个示例请求会将 Vehicle.costPerHour 替换为全局 ShipmentModel.globalDurationCostPerHour，会针对任何给定车辆，优先考虑总耗时较短的解决方案。系统还会提高 shipment[1] 的处罚成本，以降低其被跳过的可能性。
查看使用 globalDurationCostPerHour 的请求示例
{
"model": {
"globalStartTime": "2023-01-13T16:00:00-08:00",
"globalEndTime": "2023-01-14T16:00:00-08:00",
"globalDurationCostPerHour": 150.0,
"shipments": [
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.789456,
"longitude": -122.390192
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 100.0
},
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.789116,
"longitude": -122.395080
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 75.0
},
{
"deliveries": [
{
"arrivalLocation": {
"latitude": 37.795242,
"longitude": -122.399347
},
"duration": "250s"
}
],
"pickups": [
{
"arrivalLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"duration": "150s"
}
],
"penaltyCost": 50.0
}
],
"vehicles": [
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerKilometer": 10.0
},
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerKilometer": 10.0
},
{
"endLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"startLocation": {
"latitude": 37.794465,
"longitude": -122.394839
},
"costPerKilometer": 10.0
}
]
}
}
结果表明，使用全局每小时费用参数会导致使用全部三辆车，而不是只使用一辆车。
使用 globalDurationCostPerHour 查看对请求的响应
{
"routes": [
{
"vehicleStartTime": "2023-01-14T00:00:00Z",
"vehicleEndTime": "2023-01-14T00:16:20Z",
"visits": [
{
"shipmentIndex": 2,
"isPickup": true,
"startTime": "2023-01-14T00:00:00Z",
"detour": "0s"
},
{
"shipmentIndex": 2,
"startTime": "2023-01-14T00:09:19Z",
"detour": "0s"
}
],
"transitions": [
{
"travelDuration": "0s",
"waitDuration": "0s",
"totalDuration": "0s",
"startTime": "2023-01-14T00:00:00Z"
},
{
"travelDuration": "409s",
"travelDistanceMeters": 1371,
"waitDuration": "0s",
"totalDuration": "409s",
"startTime": "2023-01-14T00:02:30Z"
},
{
"travelDuration": "171s",
"travelDistanceMeters": 665,
"waitDuration": "0s",
"totalDuration": "171s",
"startTime": "2023-01-14T00:13:29Z"
}
],
"metrics": {
"performedShipmentCount": 1,
"travelDuration": "580s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "400s",
"totalDuration": "980s",
"travelDistanceMeters": 2036
},
"routeCosts": {
"model.vehicles.cost_per_kilometer": 20.36
},
"routeTotalCost": 20.36
},
{
"vehicleIndex": 1,
"vehicleStartTime": "2023-01-14T00:00:00Z",
"vehicleEndTime": "2023-01-14T00:18:54Z",
"visits": [
{
"shipmentIndex": 1,
"isPickup": true,
"startTime": "2023-01-14T00:00:00Z",
"detour": "0s"
},
{
"shipmentIndex": 1,
"startTime": "2023-01-14T00:08:24Z",
"detour": "0s"
}
],
"transitions": [
{
"travelDuration": "0s",
"waitDuration": "0s",
"totalDuration": "0s",
"startTime": "2023-01-14T00:00:00Z"
},
{
"travelDuration": "354s",
"travelDistanceMeters": 1192,
"waitDuration": "0s",
"totalDuration": "354s",
"startTime": "2023-01-14T00:02:30Z"
},
{
"travelDuration": "380s",
"travelDistanceMeters": 1190,
"waitDuration": "0s",
"totalDuration": "380s",
"startTime": "2023-01-14T00:12:34Z"
}
],
"metrics": {
"performedShipmentCount": 1,
"travelDuration": "734s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "400s",
"totalDuration": "1134s",
"travelDistanceMeters": 2382
},
"routeCosts": {
"model.vehicles.cost_per_kilometer": 23.82
},
"routeTotalCost": 23.82
},
{
"vehicleIndex": 2,
"vehicleStartTime": "2023-01-14T00:00:00Z",
"vehicleEndTime": "2023-01-14T00:16:14Z",
"visits": [
{
"isPickup": true,
"startTime": "2023-01-14T00:00:00Z",
"detour": "0s"
},
{
"startTime": "2023-01-14T00:06:25Z",
"detour": "0s"
}
],
"transitions": [
{
"travelDuration": "0s",
"waitDuration": "0s",
"totalDuration": "0s",
"startTime": "2023-01-14T00:00:00Z"
},
{
"travelDuration": "235s",
"travelDistanceMeters": 795,
"waitDuration": "0s",
"totalDuration": "235s",
"startTime": "2023-01-14T00:02:30Z"
},
{
"travelDuration": "339s",
"travelDistanceMeters": 1276,
"waitDuration": "0s",
"totalDuration": "339s",
"startTime": "2023-01-14T00:10:35Z"
}
],
"metrics": {
"performedShipmentCount": 1,
"travelDuration": "574s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "400s",
"totalDuration": "974s",
"travelDistanceMeters": 2071
},
"routeCosts": {
"model.vehicles.cost_per_kilometer": 20.71
},
"routeTotalCost": 20.71
}
],
"metrics": {
"aggregatedRouteMetrics": {
"performedShipmentCount": 3,
"travelDuration": "1888s",
"waitDuration": "0s",
"delayDuration": "0s",
"breakDuration": "0s",
"visitDuration": "1200s",
"totalDuration": "3088s",
"travelDistanceMeters": 6489
},
"usedVehicleCount": 3,
"earliestVehicleStartTime": "2023-01-14T00:00:00Z",
"latestVehicleEndTime": "2023-01-14T00:18:54Z",
"totalCost": 112.14,
"costs": {
"model.vehicles.cost_per_kilometer": 64.89,
"model.global_duration_cost_per_hour": 47.25
}
}
}
在此响应中，所有三辆车都在使用中（每个 metrics.usedVehicleCount），并且每辆车都被分配一个待完成的装运。由于起始位置、结束位置和 costPerKilometer 均相同，这三辆车实际上可以互换，因此分配给哪辆车都无关紧要。
globalDurationCostPerHour 会使优化器找到整体上更短的解决方案：earliestVehicleStartTime 和 latestVehicleEndTime 之间的差异仅为 18 分 54 秒，而上一个响应中为 28 分 22 秒。也就是说，metrics.costs.model.vehicles.cost_per_kilometer 增加了，这反映了三辆二手车的总行驶距离增加了。这演示了费用模型可让您进行权衡的一种方式：
- 增加了全局时间成本：提高车辆利用率，以最大限度地缩短总完成时间，但代价是车辆的距离和在途中需要花费的时间更长。
- 车辆时间成本增加：降低车辆利用率和在途中花费的时间，但代价是整体解决方案更长。
请注意，在此示例中，globalDurationCostPerHour 值为 150.0，设为上一个示例中每辆车 costPerHour (50.0) 的三倍。此全局成本值实际上可预期三辆车将同时运行，但在实际情况下，这些假设可能无法反映现实，并且实际上可能会对结果质量产生负面影响。
如费用模型参数中所述，所有费用参数都以相同的无维度单位表示，但含义可能截然不同。通常，费用模型参数值应尽可能基于实际情况，因为像此示例中的人为费用可能会导致 API 针对与您的意图不符的目标进行优化。