NO-IO Conversion

Use the NO-IO Conversion transformation to create a new model populated with the sites, products and policies that are used in the Network Optimization solution. This model can be used in Inventory Optimization and populates only the tables required for an Inventory Optimization model. The NO-IO Conversion creates the new model, and removes records not used in any period from the Site and Customer Sourcing Policies, Production Policies and Transportation Policies tables.

Scenario items for the selected scenario are not applied to the input data that is copied to the new model. This data includes Customer Demand/Customer Orders. Keep this in mind if you have excluded records in your input tables. The output of the selected scenario is used to recreate the network policies (sourcing, production, inventory, transportation).

Multi-period models are treated as single period models after conversion to prevent all demand from being "extremely slow". While Periods are handled during conversion, multi-period tables, such as Sites Multi-Period, are not brought into the new model.

When a site-product pair or customer-product pair has only one source, the Sourcing Policy is changed to “Single Source”. In the case of multiple sources, NO-IO Conversion changes the Sourcing Policy to “Multiple Sources(Split By Ratio)” and sets the Policy Parameter to the percentage of flow that comes from the source site. For Transportation Policies with multiple source-destination-product-mode, it similarly changes the Transportation Policies Mode Rule to “SplitByRatio” and the Policy Parameter to the percentage of flow on the specific mode.

In addition to these actions, NO-IO Conversion:

• Removes Inventory Policies that do not correspond to the optimal Site Sourcing Policies.
• Removes Sites, Products, Demand and Bills Of Material records that are not associated with the optimal Site Sourcing Policies.
• Retains only the output for the scenario that you implemented.
• Creates “default” Inventory Policies in the case that the Network Optimization model had no Inventory Policies defined. These records are created for each Site-Product combination and use the default values that are populated with new Inventory Policies records.

Requirements for the source Network Optimization model:

• The model must have a feasible Network Optimization scenario with optimization outputs populated.
• Values must be populated for all required "key" values, such as Source, Destination and Product. You can use groups and filters if required. For Transportation Policies, while Product is not identified as required, you must populate it when using the converter. If the policy applies to all products, you can use the "(ALL_Products)" filter.
• All ratios should use the same scale. For example, using 63, 37 as Policy Parameters values in Site Sourcing Policies and 0.8, 0.2 in Transportation Policies does not work during conversion. In this case, the parameters in Transportation Policies should be 80, 20.
• Do not use the output of an Infeasibility Diagnosis run. For example, this problem type can include values such as "DIAGNOSTIC_SOURCE" which cannot be identified as an existing site.

The following input tables are handled during NO-IO Conversion:

The actual Groups are not copied into the destination model. Group members are used when interpreting the NO output. Options is an internal table that stores model and solver run options.

Run NO-IO Conversion

1. Select Model > Model Transformations.
2. Select NO-IO Conversion.
3. Enter or select values for the transform parameters:
   • Server Name – The current SQL Server LocalDB instance name (typically “GURU-<username>”).
   • New IO Model Name – Enter the name for the new model you want to create with the transform. The model with the transformed data is created in the folder where your current model is located.
   • Expansion Scenario – Select the scenario you want to run.
4. Click Run. The transformation runs and creates the new Inventory Optimization model.
5. You are prompted to view the newly created model. Click OK to open a file explorer window for the file path of the new model.
6. Click No when prompted to reload the model. You can open the new IO model.