<p>Dataset is divided into 7 tables, one table for
all orders that needs to be assigned a route – <i>OrderList</i> table, and 6 additional files specifying the problem and
restrictions. For instance, the <i>FreightRates</i>
table describes all available couriers, the weight gaps for each individual
lane and rates associated. The <i>PlantPorts</i>
table describes the allowed links between the warehouses and shipping ports in
real world. Furthermore, the <i>ProductsPerPlant</i>
table lists all supported warehouse-product combinations. The V<i>miCustomers</i> lists all special cases,
where warehouse is only allowed to support specific customer, while any other
non-listed warehouse can supply any customer. Moreover, the <i>WhCapacities</i> lists warehouse capacities
measured in number of orders per day and the <i>WhCosts</i> specifies the cost associated in storing the products in
given warehouse measured in dollars per unit.</p><p><br></p><p>Order ID is ID of the
order made by the customer, product ID is the specific product ID customer
ordered.</p><p><br></p><p>"tpt_day_cnt" in the FrieghtRates table means transportation day count, i.e. estimated shipping time. </p><p><br></p><p>WhCapacities correspond
to the number of orders. For example, let's say Customer 1 requests 10 units of X,
Customer 2 requests 20 units of Y. The total number of orders is 2, thus total
capacity in "whCapacity" is 2.<br></p><p><br></p><p>WhCapacities table
is the maximum number of orders that can be processed per each plant, it is not
dependant on specific products.<br></p><p></p><p><br></p><p>The OrderList
contains historical records of how the orders were routed and demand satisfied.
The whCapacities and rest of the tables are the current state constraints of
the network. Thus, we can calculate the costs of historical network and also
optimize for the new constraints. <br></p><p><br></p><p>In order to build Linear Programming (LP) model,
you would take the following from the OrderList: the product ID that needs to
be shipped, the destination port, unit quantity (for cost) and unit weight
(for weight constraints). And then use the limits of those constraints from
other tables.</p><p><br></p><p><b>Questions: </b>There is a Carrier
V44_3 in OrderList table, but it is missing in the FreightRates table? V44_3 is a carrier that was historically used for supplying given demand, but since it has been discontinued and therefore do not appear in the Freight Rates List. Also, all of the V44_3 instances are CRF - i.e. customer arranges their own shipping and hence cost is not calculated either way. <br></p>