NS3 Unit Dimension CostUnit Dimension Cost
Overview
Unit dimensional costs are used to describe costs associated with a particular dimension and the units are used by an associated transaction. Transactions may be between nodes (such as lane rates or cost models) or within a node. This same interface can be used to describe a cost per km charge between two locations (on a lane rate), or a cost of production at a certain node (such as a manufacturing cost).
Applicable models
- NS3
ns3-tbfvuwtge2iq
Unit Dimension Cost
The unit dimension cost is used to determine the cost of the quantities associated with nodes or movement transactions in the network. The quantities associated with transactions or nodes in the network are variables in the model and, as such, the specification of the contribution to the total cost is a function of the included dimension(s) as well as coefficients determining the degree to which such dimensions contribute to the overall cost.
Schema definition
message UnitDimensionCost {
repeated string dimensionIds = 1;
repeated float dimensionCoefficients = 2;
required float costPerUnit = 3;
}
Fields
- dimensionIds
- A list of dimension identifiers which should be included in the costing of the associated parent element (a lane rate, cost model or node). No more than two of the dimension ids listed may be user dimensions, but multiple constant dimensions (such as distance or time) may be included. The reason for this is to preserve linearity in the model.
- dimensionCoefficients
- A list of coefficients that should be applied to the quantities associated with the dimensions. The coefficients provided correspond to the dimensions listed in the same order in the
dimensionIds
field above. If a list of dimensional coefficients is omitted, a value of 1.0 will be assumed for each provideddimensionId
. - costPerUnit
- A cost per combined unit that should be applied to the computed quantities. The included cost forms a portion of the total cost equation for the model. When multiple dimensions are specified the total units are computed as the sum of the scalar product of
dimensionCoefficients
and the dimensional quantities. I.e. if two dimensions are provided, the total units are computed as (dim1coef1 + dim2coef2). If dimensions should be individually costed (which is the most common case as opposed to a new computed quantitiy), multiple unit dimensional costs can be provided on the transactions or nodes.
Examples
This example provides a simple unit dimensional cost which costs each unit of distance used by an amount of 0.1 monetary units.
dimensionIds: "distance"
dimensionCoefficients: 1
costPerUnit: 0.1
This example demonstrates that user dimensions (such as weight) can be linked to unit dimensional costs. This example shows a unit dimensional cost associated with a node where each 0.5 kilograms is costed at 0.75 monetary units. This is typically used to model warehouse costs (or intermediate storage) or a weight-related cost model (such as outsourced volume agreements with hauliers).
dimensionIds: "weight"
dimensionCoefficients: 0.5
costPerUnit: 0.75
This last example demonstrates combining two dimensions to form a new quantity which is then costed at 0.15 monetary units per unit.
dimensionIds: "distance"
dimensionIds: "weight"
dimensionCoefficients: 1
dimensionCoefficients: 0.001
costPerUnit: 0.15