1. For each scenario you want to run with Cost to Serve Analysis, first run Network Optimization from the Launch Pad.
2. On the Launch Pad, select Network Optimization as the Technology and Cost To Serve Analysis as the Problem Type.
3. Select the Scenario(s) to run, then click Run.
4. If complex loops are detected in the network, the Solve Summary node in the Launch Pad indicates how many loops were detected. Click Examine to review the loops in the Cost To Serve Network Loops table. For additional information, see Loops in the network.

   

5. Open the Cost To Serve Details output table. For each Customer-Product-Period combination, you see a unique Path ID. For each Start Location Name-End Location Name combination, there is a unique Lane ID.
6. Click View Costs to display each Path ID as a single record, with individual lanes and associated costs populated. For example, the first lane may be the leg from the Manufacturer to the Warehouse. In this case all column names appended with "1" apply to this lane.

The Cost To Serve fly out view is based on a model database object called “OptimizationOutputNetworkPathsDynamicView”. You can target this object directly in Tableau to provide additional analysis on the cost to serve output.

For some large models, the OptimizationOutputNetworkPathsDynamicView is too large to import successfully into the model. If you encounter this issue, you can check the Bypass Cost To Serve Dynamic View option on the Advanced Settings tab in Network Optimization Run Options. When this option is selected, the output table for the dynamic view is not generated.

Cost To Serve Analysis populates output tables (Cost To Serve Details, Cost To Serve Product Details, Cost To Serve Network Loops). It also creates a view based on the data in the scenario that is run. The columns in this view will vary based on the number of echelons in the solution. Depending on the size of the network in the solution, creating this view can take some time to complete.

1. Define a group for each set of customers or products you want to use to limit cost to serve output. For example, create a group called "PrimaryCustomers" that includes the subset of customers you want reported.
2. In the Config_NO table, enter a record for each filter type you plan to use with Cost To Serve Analysis. The values in the table will be as follows:
   • ParameterName: Enter either CTSFilter_Sites when specifying a customer group or CTSFilter_Products when specifying a product group
   • ParameterValue: Enter the name of the associated product, product group, site, site group (such as Primary Customers).
   • Status: Set the value to Include if you want the filter to be applied to cost to serve output. Set the value to Exclude if the filter does not apply.
3. Using the Launch Pad, run Cost To Serve Analysis on your selected scenario(s).
4. When complete, review the output to see the limited results. For example, if you limited the customers using a group, there are records for only the group members in the Cost To Serve Details output table.

1. In the Config_NO table, enter a record for each percentage filter you plan to use with Cost To Serve Analysis. The values in the table will be as follows:
   • ParameterName: Enter the percentage filter name, such as CTSFilter_MinCostPercentage. The filter will be a minimum or maximum for either cost or flow.
   • ParameterValue: Enter the minimum or maximum value, such as 0.9.
   • Status: Set the value to Include if you want the filter to be applied to cost to serve output. Set the value to Exclude if the filter does not apply.
2. Using the Launch Pad, run Cost To Serve Analysis on your selected scenario(s).
3. When complete, review the output to see the limited results. For example, if you limited the customers using a group, there are records for only the group members in the Cost To Serve Details output table.