OptimizeToursRequest 消息（REST、gRPC）包含许多与费用相关的属性。这些费用参数共同表示请求的费用模型。费用模型可捕获请求的许多高级优化目标，例如：
- 优先采用更快的
Vehicle路线，而非较短的路线，反之亦然 - 确定分发
Shipment的费用是否与Shipment完成操作的价值相一致 - 仅在时间范围内执行取货和送货服务才具有成本效益
查看包含费用的示例请求
{
"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": 40.0,
"costPerKilometer": 10.0
}
]
}
}
Vehicle 项费用属性
Vehicle 消息（REST、gRPC）具有若干费用属性：
Vehicle.cost_per_hour：表示每小时运营车辆的费用，包括运送、等待、访问和停工时间。Vehicle.cost_per_kilometer：表示车辆行驶的每公里费用。Vehicle.cost_per_traveled_hour：表示仅在运送途中运营车辆的费用，不包括等待时间、访问时间和休息时间。
这些成本参数允许优化器在时间与旅行距离之间进行权衡。优化路线产生的费用在响应消息中显示为 metrics.costs：
随着 costPerHour 的增加，优化器会尝试查找速度更快的路由，但可能不是最短路由。在此示例中，最快路线恰好是最短路线，因此更改费用参数几乎没有影响。
Shipment 项费用属性
Shipment 消息（REST、gRPC）还有几个费用参数：
Shipment.penalty_cost表示因跳过装运而产生的费用。Shipment.VisitRequest.cost表示特定自提或送货费用，主要用于在单个运单的多个自提或配送选项之间进行费用权衡。
Shipment 费用参数使用与 Vehicle 费用参数相同的无维度单位。完成 Shipment 所产生的费用超出了其罚款费用，因此 Shipment 未包含在任何 Vehicle 的路由中，而是显示在响应消息的 skipped_shipments 列表中。
ShipmentModel 项费用属性
ShipmentModel 消息（REST、gRPC）包含单个费用属性 globalDurationCostPerHour。系统会根据所有车辆完成 ShipmentRoute 所需的总时间收取这笔费用。增加 globalDurationCostPerHour 会优先完成所有运单。
路线优化响应费用属性
OptimizeToursResponse 消息（REST、gRPC）具有费用属性，表示完成 ShipmentRoute 的过程所产生的费用。metrics.costs 和 metrics.totalCost 属性表示响应中所有路由产生的费用单位数。每个 routes 条目具有 routeCosts 和 routeTotalCosts 属性，分别代表该特定路线的费用。
查看对示例请求的响应（包含费用）
{
"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": 18.911111111111111
},
"routeTotalCost": 52.441111111111113
}
],
"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": 57.441111111111113,
"costs": {
"model.vehicles.cost_per_kilometer": 33.53,
"model.vehicles.cost_per_hour": 18.911111111111111,
"model.shipments.penalty_cost": 5
}
}
}
在示例响应中，顶级 metrics.costs 为：
{
"metrics": {
...
"costs": {
"model.vehicles.cost_per_hour": 18.911111111111111,
"model.vehicles.cost_per_kilometer": 33.53,
"model.shipments.penalty_cost": 5
}
}
}
model.shipments.penalty_cost 值表示因跳过的运单而产生的费用。skippedShipments 属性会列出跳过了哪些运单。
在此示例中，仅跳过示例请求中的 model.shipments[1]。model.shipments[1] 的惩罚因子为 5 个单位，与示例响应中的总 model.shipments.penalty_cost 键一致。与 Vehicle 的 40.0 costPerHour 和 10.0 costPerKilometer 相比，运单的 penaltyCost 较低，因此跳过运单的性价比要高于完成运单。
高级主题：费用和软约束
多个 OptimizeToursRequest 消息（REST、gRPC）属性表示“软约束”，这些约束条件无法得到满足，就会产生费用。
例如，车辆 LoadLimit（REST、gRPC）限制条件具有 softMaxLoad 和 costPerUnitAboveSoftMax 属性。两者相结合产生的费用与超过 softMaxLoad 的负载单元成正比，因此只有在从费用的角度来看，这才有意义时，才会超出此限制。
同样，TimeWindow 限制条件（REST、gRPC）具有 soft_start_time 和 soft_end_time 属性，其对应的 cost_per_hour_before_soft_start_time 和 cost_per_hour_after_soft_end_time 是根据 TimeWindow 中受限事件的发生早或晚时间来引发的。
与所有费用模型参数一样，软约束费用与其他费用参数以相同的无维度单位表示。
加载需求和限制中详细介绍了 LoadLimit 限制条件。取货和送货时间范围限制中详细介绍了 TimeWindow 限制条件。