Important notes:

• Several columns are no longer available in the user interface. These are columns that are not currently in use by a solver. The columns are still defined in the model database tables. Review columns that have a Description of Change value of "Removed from UI (not currently in use)".

• Please review columns that have a Description of Change value of "Data Type change", "Column removed" or "Change in Required". If you use these columns in a workflow, you may need to adjust the workflow to support the new data type or requirement.

Input Tables

Table	Column	Description of Change	Model Database Table Name	Model Database Column Name	Data Type	Required
Input Tables
OptionsSnapshot (Table not displayed in the UI)	ID	New table/column	OptionsSnapshot	ID	Integer	Yes
	SnapshotID	New table/column	OptionsSnapshot	SnapshotID	GUID	Yes
	Option	New table/column	OptionsSnapshot	Option	Text	Yes
	Value	New table/column	OptionsSnapshot	Value	Text	No
SnapshotLookup (Table not displayed in the UI)	ID	New table/column	SnapshotLookup	ID	Integer	Yes
	SnapshotName	New table/column	SnapshotLookup	SnapshotName	Text	Yes
	SnapshotID	New table/column	SnapshotLookup	SnapshotID	GUID	Yes
	Type	New table/column	SnapshotLookup	Type	Text	Yes

Output Tables

Table	Column	Description of Change	Model Database Table Name	Model Database Column Name	Data Type
Output Tables
Work Center Queue Depth Detail	Product	Renamed to Work Center	SimulationOutputWorkCenterQueueDepthDetail	WORKCENTER	Text
Cost To Serve Details	Refundable Tax	New column	OptimizationOutputNetworkPathDetails	RefundableTax	Money
	Non-Refundable Tax	New column	OptimizationOutputNetworkPathDetails	NonRefundableTax	Money
Path Summary	Refundable Tax	New column	OutputPathsSummary	RefundableTax	Money
	Non-Refundable Tax	New column	OutputPathsSummary	NonRefundableTax	Money
OptimizationOutputCostAllocation_Lane (Table not displayed in the UI)	Refundable Tax	New column (not displayed in the UI)	OptimizationOutputCostAllocation_Lane	RefundableTax	Money
	Non-Refundable Tax	New column (not displayed in the UI)	OptimizationOutputCostAllocation_Lane	NonRefundableTax	Money
Cost To Serve Customer Summary	Customer	New table/column	OutputCostToServeCustomerSummary	CustomerName	Text
	Total Paths	New table/column	OutputCostToServeCustomerSummary	TotalPath	Float
	Max Path Length	New table/column	OutputCostToServeCustomerSummary	MaxPathLength	Float
	Min Path Length	New table/column	OutputCostToServeCustomerSummary	MinPathLength	Float
	Average Path Length	New table/column	OutputCostToServeCustomerSummary	AvgPathLength	Float
	Total Revenue	New table/column	OutputCostToServeCustomerSummary	TotalRevenue	Money
	Total Cost	New table/column	OutputCostToServeCustomerSummary	TotalCost	Money
	Total Profit	New table/column	OutputCostToServeCustomerSummary	TotalProfit	Money
	Total Lane Cost	New table/column	OutputCostToServeCustomerSummary	TotalLaneCost	Money
	Total Site Cost	New table/column	OutputCostToServeCustomerSummary	TotalSiteCost	Money
	Total Site Product Cost	New table/column	OutputCostToServeCustomerSummary	TotalSiteProductCost	Money
	Total Other Cost	New table/column	OutputCostToServeCustomerSummary	TotalOtherCost	Money
	Total Flow Rate	New table/column	OutputCostToServeCustomerSummary	TotalFlowRate	Float
	Total Revenue Rate	New table/column	OutputCostToServeCustomerSummary	TotalRevenueRate	Float
	Total Profit Rate	New table/column	OutputCostToServeCustomerSummary	TotalProfitRate	Float
	Total Weighted Service Time	New table/column	OutputCostToServeCustomerSummary	TotalWeightedServiceTime	Float
	Total Flow Risk	New table/column	OutputCostToServeCustomerSummary	TotalFlowRisk	Float
	Total Revenue Risk	New table/column	OutputCostToServeCustomerSummary	TotalRevenueRisk	Float
	Total Profit Risk	New table/column	OutputCostToServeCustomerSummary	TotalProfitRisk	Float
	Scenario ID	New table/column	OutputCostToServeCustomerSummary	ScenarioID	Integer
	Sub-Scenario ID	New table/column	OutputCostToServeCustomerSummary	StepNumber	Integer
Cost To Serve Finished Goods Summary	Product	New table/column	OutputCostToServeFinishedGoodsSummary	ProductName	Text
	Total Paths	New table/column	OutputCostToServeFinishedGoodsSummary	TotalPath	Float
	Max Path Length	New table/column	OutputCostToServeFinishedGoodsSummary	MaxPathLength	Float
	Min Path Length	New table/column	OutputCostToServeFinishedGoodsSummary	MinPathLength	Float
	Average Path Length	New table/column	OutputCostToServeFinishedGoodsSummary	AvgPathLength	Float
	Total Revenue	New table/column	OutputCostToServeFinishedGoodsSummary	TotalRevenue	Money
	Total Cost	New table/column	OutputCostToServeFinishedGoodsSummary	TotalCost	Money
	Total Profit	New table/column	OutputCostToServeFinishedGoodsSummary	TotalProfit	Money
	Total Lane Cost	New table/column	OutputCostToServeFinishedGoodsSummary	TotalLaneCost	Money
	Total Site Cost	New table/column	OutputCostToServeFinishedGoodsSummary	TotalSiteCost	Money
	Total Site Product Cost	New table/column	OutputCostToServeFinishedGoodsSummary	TotalSiteProductCost	Money
	Total Other Cost	New table/column	OutputCostToServeFinishedGoodsSummary	TotalOtherCost	Money
	Total Flow Rate	New table/column	OutputCostToServeFinishedGoodsSummary	TotalFlowRate	Float
	Total Revenue Rate	New table/column	OutputCostToServeFinishedGoodsSummary	TotalRevenueRate	Float
	Total Profit Rate	New table/column	OutputCostToServeFinishedGoodsSummary	TotalProfitRate	Float
	Total Weighted Service Time	New table/column	OutputCostToServeFinishedGoodsSummary	TotalWeightedServiceTime	Float
	Total Flow Risk	New table/column	OutputCostToServeFinishedGoodsSummary	TotalFlowRisk	Float
	Total Revenue Risk	New table/column	OutputCostToServeFinishedGoodsSummary	TotalRevenueRisk	Float
	Total Profit Risk	New table/column	OutputCostToServeFinishedGoodsSummary	TotalProfitRisk	Float
	Scenario ID	New table/column	OutputCostToServeFinishedGoodsSummary	ScenarioID	Integer
	Sub-Scenario ID	New table/column	OutputCostToServeFinishedGoodsSummary	StepNumber	Integer

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of the January 2025 release (R41), this includes models from releases back to the R39 release (schema version 407000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. As of R41, support is ending for the following schema version, as well as older model schemas:

• Release R38 (schema 406000)

Removal of Modeler Graphs

As part of the transition to the Data Visualizations feature, Coupa removed the Modeler Graphs feature on the Supply Chain platform on January 18, 2025.

Modeler default for Network Optimization is now the Next Generation solver

When solving using Network Optimization, the default solving engine now uses the Next Generation (Next Gen) solver. Previously, the Next Gen solver was available but not selected by default. This solver provides improved performance for most models and a “round robin” method of processing requests. It currently applies only to Network Optimization.

If you want to use the previous solvers, turn off the “Enable Next Generation Solving Engine” switch in the Modeler Launch Pad before running scenarios.

Rapid Network Explorer

When building scenarios to evaluate changes to your network, long running scenarios can be a challenge to providing results to key stakeholders in a timely manner. The Rapid Network Explorer (RNE) is designed to support small changes, such as adjustments to transportation or production costs, then solving without generating the full model again. This significantly reduces the time to return results, allowing you to explore a number of changes in a short period of time.

Run Network Optimization on a scenario to be used as the base data for RNE. You then define rapid scenarios, with items that adjust specific RNE eligible columns, such as demand quantity and variable transportation cost. When you run the Rapid Solve problem type, the items in the rapid scenario are applied to the base scenario results and output is returned to the model.

The RNE Intensity option lets you control the extent to which decision variables in the base scenario are fixed when running the rapid solve. A higher value means more decision variables are constrained, leading to a quicker solution. A lower value opens up the base data by not constraining as many decision variables.

Optimize networks to minimize risk level

When you populate Risk Profiles in your model, Network Optimization outputs a composite risk score for the sites in the network. However, this risk score does not affect the optimization results. In this release, you can use risk as a constraint and as an objective for Network Optimization. Updates to input tables, sequential objectives, constraints, and parameters enable Network Optimization to minimize risk and respect maximum risk levels.

You can define a Maximum Risk constraint value per product in the Products table. The product risk is the weighted average of the product flow through the sites based on each site’s risk score. The site risk score is based on the weighted average of user-entered scores in the Risk Profile table when a Risk Profile is assigned to a site. You can also constrain risk at the network level with the Maximum Network Risk option in Network Optimization Options.

To apply risk as part of the objective, create one or more Sequential Objective records targeting the new risk-based objectives, then run Sequential Optimization:

• Total Network Risk

• Maximum Network Risk

• Maximum Product Risk

New output tables and columns report the aggregated risk scores and provide percentage summaries of high, moderate, and low risk flows in the solution.

Changes to scores in Risk Profiles

The four Custom Score columns in the Risk Profiles table are now evaluated on a scale of 0 to 100 where higher scores signify higher risk. Previously, a high score signified a low risk.

Cost To Serve features

Additional columns are available in cost to serve-related output tables. The Site Variable Cost and Space Expansion Cost are now included in the Network Path Details and Path Summary output tables.

Space Expansion Cost is also included as an input when running Cost To Serve Analysis.

New configuration parameters have been added for Cost To Serve Analysis:

• CTSFilter_TopProdsByCostPercentage - The final products are ranked by the cost related to them, then the percentage entered for this parameter is used to select the top x products. Cost To Serve Analysis is run on this smaller set of products, resulting in fewer paths in the output. The value is between 0 and 1.

• CTSFilter_TopProdsByProfitPercentage - The final products are ranked by the profit related to them, then the percentage entered for this parameter is used to select the top x products. Cost To Serve Analysis is run on this smaller set of products, resulting in fewer paths in the output. The value is between 0 and 1.

Populate these parameters in the Config_NO table and set the Status to “Include” to use them in Cost To Serve Analysis.

Network Optimization dynamic termination settings

Network Optimization supports dynamic termination settings, enabling you to stop a solve based on settings such as the maximum time since the last solution was found, the maximum percent of memory consumed by the solve, and others. These settings support better tuning of solve terminations.

The settings are available on the Termination Settings tab in Network Optimization Options:

• Maximum Time Since Last Solution – Stops the model after no better solution has been found for the time entered (in seconds).

• Maximum Time Since Last Improvement – Stops the model after no better gap has been found for the time entered (in seconds).

• Dynamic Percent Gap - Allows the termination percent gap to change over the solving process. Define a two-step function where the first value in each pair is the run time (in seconds) and the second is the gap percentage.

• Dynamic Absolute Gap - Allows the termination percent gap to change over the solving process. Define a two-step function where the first value in each pair is the run time (in seconds) and the second is the absolute gap.

• Max Memory Consumption Percent - Forces the solve to stop after system memory consumption reaches the percentage defined by the limit.

Bing support in Transit Matrix Calculate Paths

Bing is supported as the default provider when you Calculate Paths in the Transit Matrix table. When using Bing, you also have the option to “Avoid Ferry Route Calculation If Possible”. When this option is selected, Bing seeks routes that do not use ferries.

Display list of visualizations associated with a model

Data Visualizations now supports three workbooks per model asset. In Modeler, when you select Data Visualizations, workbooks that are currently defined for the model are displayed in the Data Visualization pane. To open a workbook, click on the name – the workbook is opened in Data Visualizations in a new browser tab.

Click New Workbook to create a new workbook for the model.

NO – IO Conversion and Model Expansion support solver selection

The two model transformations, NO – IO Conversion and Model Expansion, now provide solving engine selection when the model is run. This enables you to use more powerful solving engines for complex, memory intensive models.

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of the September 2024 release (R40), this includes models from releases back to the R38 release (schema version 406000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. As of R40, support is ending for the following schema version, as well as older model schemas:

• Release R37 (schema 405000)

Next generation solver for Network Optimization

As Coupa continues to innovate and deliver faster solutions to our customers, Network Optimization now offers a next generation (Next Gen) deployment of the solver as an option when running models in Modeler. The Next Gen solver offers the same Network Optimization technology, with improvements to the processing of models.

Benefits of the Next Gen solver include:

• Improved performance – In many cases, models solve faster with the Next Gen solver than the previous solver. This may not affect models that already run quickly but is more evident with longer running models.

• “Round Robin” processing of requests – The Next Gen solver will loop through requests by customer. This prevents cases where a customer sends a large number of requests that effectively block the next customer’s requests from starting right away. The solver executes a request from the first customer, then moves on to the next customer and executes a request. This continues for all customers in the queue. Once it has been through all customers, it loops back to the first customer and will continue to take requests in this manner as long as there is available memory and CPU. As resources are freed up, it processes additional requests.

• Removal of strict limitation on the maximum number of design engines – The Next Gen solver will not have the same cap of the available number of design engines that can be accessed at one time. As a result, the Next Gen solver can scale more effectively than the previous solver when large numbers of requests are made.

Transit Matrix route calculation

The Transit Matrix provides a way to use accurate road distance and travel time values when solving your model. You can now generate source-destination connections in the Transit Matrix table in Modeler using either Transportation Policies or Site and Customer locations. Filters let you control which connections are generated. Once the Transit Matrix table has been populated, you can then use Straight Line Plus Circuity to calculate the Distance and Travel Time on the route.

Cost To Serve updates

New output tables provide additional information pertaining to the enhanced Cost To Serve Analysis. The Cost To Serve Network Summary gives scenario-level metrics about the paths created by Cost To Serve, including path lengths, costs, revenue, and profit values. The Path Summary has path-level details, including many cost metrics, revenue, and profit values.

Sequential Objectives for spatial modeling

A set of objectives is available in the Sequential Objectives table for use with spatial modeling:

• Maximum Site Expansion

• Minimum Site Expansion

• Maximum Storage Space Expansion

• Minimum Storage Space Expansion

• Maximum Shipping Space Expansion

• Minimum Shipping Space Expansion

In support of these objectives, Storage Space and Shipping Space columns have been added to the Sequential Objectives table.

Multi-stop dock door scheduling

Dock door scheduling is now supported for multiple stops on a route. The previous limitation that a dock door is applied only to one stop on a route has been removed. New columns in the Customers table also let you define the Number of Dock Doors and Dock Door Reset Time at customer locations. Transportation Optimization considers these constraints and assigns docks doors on the route for both site and customer stops.

The new Dock Door Assignment output table summarizes dock door use at site and customer locations for each route.

Improved model upload

When you use the upload feature in Modeler , you see the Data Management Upload feature in a new browser tab. This feature provides improved visibility, control, and performance during file uploads. In addition, you can now upload multiple assets at one time and track their progress.

When selecting the file to upload, you can optionally change the name for the uploaded asset.

Data Management displays a progress link above the assets table. Click the link to review all uploads currently in progress. If needed, you can pause the upload and resume at a later time. When resumed, the upload continues from the point where it was paused, rather than requiring a new upload.

Visualization support for Inventory Optimization and Transportation Optimization

When creating a workbook for Data Visualizations, you select the Technology Type to be used. This is one of: Network / Inventory Optimization or Transportation Optimization. The visualizations load script includes the correct tables for the selected Technology Type.

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of May 2024 release (R39), this includes models from releases back to the R37 release (schema version 405000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. As of R39, support is ending for the following schema version, as well as older model schemas:

• Release R36 (schema 404000)

Direct access to Data Visualizations

You can create visualization workbooks based on data in your Supply Chain models. You can access Data Visualizations directly from your model when it is open in Modeler using the Visualizations icon in the Analysis section of the Navigation pane. If there is already a workbook defined for the model, the workbook is opened in a new browser tab. If there is no workbook defined, you see a flyout where you enter the name for the workbook. When you click Save, the workbook is created and opened in Data Visualizations.

New Allocation Constraint tables

A set of Network Optimization allocation constraints tables were added to the model schema in the previous release. In this release, the tables are available in the user interface and will be used by Network Optimization:

• Flow Allocation Constraints

• Inventory Allocation Constraints

• Production Allocation Constraints

Use these tables to constrain the allocation of flow, inventory, or production. For example, you can define a flow allocation constraint that requires:

The flow quantity through the sites specified by MexicoSites must be at least 40% of the flow quantity through all sites.

In this case you define a set containing the sites in Mexico and evaluate it against a filter column where the value contains all sites. The constraint is defined with a Percentage (the set compared to the filter), a constraint Type (Min, Max, Fixed, Cond_Min, Cond_Fixed) and a Basis (Quantity, Weight, or Volume).

Max Capital Investment option update

The Max Capital Investment option is no longer displayed on the Technology Constraints tab in NO Run Options. You now control this value using the MAX_CAPEX value in the Config_NO table. Enter a positive value and set the Status to “Include” to use the maximum capital investment constraint.

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of January 2024 release (R38), this includes models from releases back to the R36 release (schema version 404000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. As of R38, support is ending for the following schema versions, as well as older model schemas:

• Release R34 (schema 402000)

• Release R35 (schema 403000)

Driver Scheduling duty duration

The driver Duty Duration has been added to the Driver Summary output table for Transportation Optimization.

Improved cost allocation in shipment output tables

Shipment output tables now define both Distance-Based Allocated Cost and Time-Based Allocated Cost. The new Time-Based Allocated Cost enables you to account for excessively long load and unload times. This uses the product of the shipment’s quantity and the travel time on the route combined with load and unload times. These values are in the Shipment Output and Delivered Shipments output tables for Transportation Optimization.

Start and end of route service time input for Transportation Assets

You can define specific service times that apply to the start and end of each route. These service times can account for pre- and post-route activities such as documentation and vehicle refueling. Use the Start Of Route Service Time and End Of Route Service Time columns in Transportation Assets to define the time for these activities.

Duplicate constraint names excluded from Network Optimization input files

If you defined multiple constraints in a table with the same name, duplicate constraint names were being written to input files. In this case, Network Optimization uses the last constraint record written to the input file and ignores all duplicates. This behavior has been changed so that in the case of duplicate constraint names, only the first record is written to the input file. The duplicates are reported in the ErrorLog.txt file

Spatial constraint costs in Cost To Serve

Expansion costs, the Fixed Operating Space Expansion Cost from Sites and the Floor Expansion Cost from Site Storage Spaces and Site Shipping Spaces, are currently included in Other Cost in Cost To Serve Details. The Site Variable Cost from Sites is currently included in the Total Cost value.

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of September 2023 release (R37), this includes models from releases back to the R34 release (schema version 402000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. As of R37, support is ending for the following schema version, as well as older model schemas:

• Release R33 (schema 401000)

Technology display mode

The Technologies tab in Model Settings provides you with a way to limit the input and output information displayed based on the solver technology (or technologies) you use. For example, if you are currently working on a model for use with Network Optimization only, you do not need to see the tables and columns that are used only by Transportation Optimization, such as Rates and the Service Time columns on Sites. Turn on only the Network Optimization switch to hide information that applies to Inventory Optimization, Transportation Optimization and Simulation.

In addition, you can use the Basic mode to further limit the displayed tables and columns to only those required and most typically used when modeling.

Early/late demand updates

The Customer Order Fulfillment table is no longer read-only. The Fulfillment ID,Single Source Fulfillment and Single Period Fulfillment columns in Customer Demand and Customer Orders are also no longer read-only. The Fulfillment ID column in both the Customer Demand and Customer Orders tables uses values defined in the Fulfillment ID column in the Customer Order Fulfillment table.

Updates to Sequential Objectives

A number of new Objective values are available in the Sequential Objectives input table:

Penalty Cost	Customer Revenue	Fractional Return Destination Constraints
Total Closing Cost	Site Demand	Return Flow Balance Constraints
Total Duty Cost	Inventory Process	Return Process
Total Expression Based Cost	Maximum Number of Transportation Asset	Single Return Destination Constraints
Total Fixed Startup Cost	Batch Flow	Sourcing Process
Total Inbound Warehousing Cost	Production Process	Process BOM Connection
Total Outbound Warehousing Cost	Fractional Process Constraints	Process To Process Relation
Total InTransit InvCost	Single Process	Transportation Process
Total TPAsset Cost	Process Step Balance Constraints
Total Work Resource Cost	Single Process Step

Several Objective values have been removed, as they are not used by the Network Optimization solver:

• Make Processes Single Sourcing

• Make Processes Fractional Sourcing

• Make Process Flow Single Destination

• Make Process Flow Fractional Destination

If your Sequential Objectives table includes any of the objective values that have been removed, you will see a warning in the ErrorLog.txt when you run the model. However, this is expected since the solver does not use them.

Control over Cost To Serve internal table population

When you run Network Optimization, a number of internal tables are populated with data that is used by Cost To Serve Analysis. These tables can have significantly large numbers of records. You can use the new SKIP_COST_ALLOCATION_OUTPUT parameter in the Config_NO table to prevent these tables from being populated if you do not plan to use Cost To Serve Analysis. Make sure the Parameter Value is 1 and the Status is "Include" to enable this behavior.

Shipment-based rates

Transportation Optimization supports Per Unit Cost and Discount Rate values at the route level, where each shipment on the route is assigned the same cost and rate. You can use shipment-based rates where different costs and rates are allowed for each shipment on a route. This functionality enables you to define route costing and rating with increased granularity. It also provides a way to model LTL aggregation, where shipments with different LTL rates can be combined on a single route. First you assign a classification (Class Name) to the shipments, then create Per Unit Cost and Discount Rate values for each unique asset-source-destination-class combination in the Shipment-Based Rate table.

Drone modeling updates

You can now constrain the maximum time that a drone waits at a location. Also, the Sortie ID has been added to the Shipment Output and Delivered Shipments output tables.

Driver scheduling updates

Additional columns have been added to let you constrain the Driver Scheduling problem type to adhere to regional driver requirements, such as US DOT regulations. You define the drive time for routes that are the source for Driver Scheduling. You can then constrain the maximum drive time that can be incurred per shift for a driver class.

SCDP 36.1.0 Validation for user defined columns

Input table validation has been extended to user defined text columns that are defined with a specific Usage, such as "Customers" and "Status". This feature applies to user defined columns in standard tables and in user defined tables.

Platform support for model versions

The Supply Chain platform supports models with a database schema of up to 1 year old. As of release 36.0.0, this includes models from releases back to the R34 release (schema version 402000). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. Support is ending for the following schema versions:

• Release R30 (schema 303007)

• Release R31 (schema 303009)

• Release R32 (schema 400000)

• Release R33 (schema 401000)

According to our standard support policy, we plan to retire Design Engines that are 1 year old or older. In an effort to provide advance notice, as part of the R37 release (planned for September 2023), we will be shutting down the R34 Design Engines.

Control over data formats in tables

Date, numeric, and currency values in tables can be difficult to read if not in a format that is typical for the user. The Data Formats tab in Model Options provides options that let you control the format for each of these types of values. For numeric and currency values, you set the number of decimal places, how negative values should be displayed and whether to include the thousands separator. Currencies also support options that let you select the position of the currency symbol, or hide the symbol. Dates offer short and long date and time formats, and an option to exclude the time component.

User defined tables and columns

You can create new user defined input tables that can, for example, serve as inputs to solver customizations or as data sources for input pipes. These tables are maintained when models are upgraded for new product releases.

User defined columns let you add columns to existing input tables or to user defined tables. You can use these columns for filtering tables and for storing additional information not covered by standard columns. You specify the data type for each column: text, integer, decimal or date. For the text columns, you can optionally specify a usage such as "Customers" or "Products". When a usage has been applied, the record names, groups names and filter names defined for the usage will be available in the dropdown list for the user defined column value. This behavior is similar to what is available in the Customer column in the Customer Demand input table. User defined columns can be deleted as needed.

Appending records with table import

When using the Import feature to import records into a Modeler input table, you now have the choice of whether to replace all existing records or append the imported records to those already in the table. When appending, if any of the records from the source result in records that would violate duplicate entries in the table, the import will fail.

Early and late demand modeling

Early and late demand modeling allows you to specify demand records that can be served outside the demanded period. You can associate penalty costs for early/late fulfillment as well as limits on demand timing. You can prioritize demand, allowing models to be broken down to reduce overall complexity.

New columns in the Customer Demand and Customer Orders table let you define the demand timing and associated penalties. In Customer Demand, use Periods Allowed Early and Periods Allowed Late and the corresponding delivery penalty cost columns. Similarly, in Customer Orders, use Time Allowed Early and Time Allowed Late and the corresponding delivery penalty cost columns.

Columns have been added in a number of Network Optimization output tables, providing details about early and late demand fulfillment, including penalty costs. This information is available in Network Summary, Financial Summary, Network Organization Summary, Network Customer Summary, Network Product Summary and Customer Demand Summary.

Model decomposition

The decomposition method allows you to break a large model into smaller pieces and solve them more efficiently. For large models, this method can help reduce both solving time and memory usage significantly. Model decomposition extracts solvable sub-models from the original model by analyzing the complex relationship across all supply chain elements: products, sites, lanes, demand, bills of material, work centers, processes and constraints. In this release, the main focus is on the constraints related to products, so each sub-model will have a different subset of the products. Each sub-model contains only its own data which makes the problem size much smaller. After solving all the sub-models, the solution of the original model is obtained by merging the output of all the sub-models.

Sequential objectives

Objectives have been updated in the Sequential Objectives table:

• "Total CO2 Emission" has been renamed to "Total CO2 Cost" to reflect the fact that this objective is based on the cost associated with CO2.

• "Total CO2" has been added. This objective is based on the weight of carbon emissions.

• "Carbon Footprint" has been renamed to "Maximum Carbon Footprint" since this is based on Maximum Carbon Footprint in the Greenhouse Gases table.

Predicted solve time

When running Network Optimization models, it can be hard to know the complexity of the problem and how long it will take to solve. The solve process includes an improved method to both identify a solve time range and highlight complexities in the model that may contribute to longer solve times. This information can help you understand what drives model complexity and how this affects solve times. The predictive information is displayed in several places:

• The Scenario Status Queue on the Modeler landing page

• The Scenario Queue on the Modeler Launch Pad

• The General tab for a Queue Management Models

• The solve log that is available in Queue Management

Drone modeling

Transportation Optimization includes the capability to model drones with ground transportation assets, enabling users to deploy drones that make deliveries in coordination with trucks. The trucks serve both as a mobile depot, where drone launches and retrievals are performed, and a delivery asset. Transportation Optimization determines where and how to incorporate drones into the logistics operations to improve last-mile delivery and reduce cost.

Drone truck delivery supports a number of features, including:

• Define various drone types by payload, speed and battery

• Assign drone types to ground vehicles as potential companions in performing delivery

• Allow for fixed and linear endurance models to determine the effective flight range

• Overwrite point to point flight distance and time with transit matrix

Driver scheduling enhancements

New inputs have been added to improve control over the Driver Scheduling problem type in Transportation Optimization:

• Driver Availability - Use this new input table to define the number of drivers per driver class available at a site. You can also constrain the time window for which the driver class is available.

• Routes - The Asset Origin column has been added to this input table to identify where the transportation assets originate for driver scheduling. This value is now populated in a number of output tables when the model is solved.

A new Driver Utilization output table provides a summary of drivers available and used per site - driver class combination.

Closing Cost data type change

The data type for the Fixed Closing Cost column in the Sites, Sites Multi-Period, Work Centers, and Work Centers Multi-Period tables has been changed from float to text. This change is to support the use of currencies when defining the closing cost.

Map performance improvements

Map display performance has been updated to use batched requests. This helps to prevent the display of the map layer and associated table grid from timing out with large numbers of records.

Updated default value for Post Process Random Lead Time

The default for the Post Process Random Lead Time option on the Safety Stock Optimization Advanced tab in Inventory Optimization options has been changed from unchecked (off) to checked (on). This applies to new models and existing models where you have never set the option. If you have manually set the option, the value will not be changed during model upgrade. Most IO models have lead time variation, so it is typically expected that the option should be selected. This change ensures that you actively turn it off if not needed.

Tables handled during NO-IO Conversion

NO-IO Conversion handles the following tables during the model transformation:

Products, Sites, Customers, Periods, Modes, Bills of Material, Bill of Material Assignments, Customer Orders, Customer Demand, User Defined Customer Forecast Profile, User Defined Site Forecast Profile, Production Policies, Inventory Policies, Site Sourcing Policies, Customer Sourcing Policies, Transportation Policies, Transit Matrix, Group Members, Options.

For this release, tables were added in addition to those handled in the previous release. These specific tables are:

• User Defined Customer Forecast Profile

• User Defined Site Forecast Profile

• Transit Matrix

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.

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.

Getting Started page updates

Links on the Modeler Getting Started page have been updated to correctly reflect the locations for Coupa University and the Coupa Support Portal.

Platform support for model versions

The Supply Chain platform supports models with a database schema of up to 1 year old. As of release 35.0.0, this includes models from releases back to the R30 release (schema version 303007). Models with unsupported schemas must be upgraded prior to solving, modeling, using with apps or solving on the cloud. Support is ending for the following schema versions:

• 302000 (Release 2020.09)

• 303001 (Release 2020.12)

Model options

You now have access to model options that control a number of features in your model. The options include:

• General - model horizon, inventory carrying cost, model culture and others.

• Scenario - define an alternate name for the Baseline scenario.

• Units and Currency - default values for units of measure (such as weight and distance) and currency.

Model Options are located in the Model Actions menu to the left of the Launch Pad button.

Input table validation

Modeler supports validation of data in input tables, in cases such as columns that use a specific set of accepted values or values from another table. You can validate an individual table, or validate all input tables in the model. When validation is complete, invalid values are highlighted and the rows containing invalid values are flagged. You can apply a filter to display only those records with invalid values or those with no invalid values. In the input table navigation pane, tables with records that have invalid values are flagged, as are the groups to which the input tables belong.

Spatial modeling

Network Optimization includes the capability to model space within sites, enabling you to determine site size based on dimensional requirements (floor area). You can define spaces to align with specific functions within the location, such as storage, shipping and offices. The space definitions include fixed and variable costs and CO2 consumption rates. They also capture inventory considerations and overall constraints, such as minimum and maximum expansion limits.

Spatial modeling supports a number of features, including:

• Assess sites based on available space with associated costs for startup and operating expenses.

• Allow for variable space usage based on the activity in the space, including minimum and maximum allowances based on throughput of specific products.

• Constrain sites and spaces by the total allowable space.

• Expand sites and spaces while considering expansion costs and increased operating costs and CO2 consumption.

• Define obsolete/unhealthy stock as a quantity or as a percentage of "healthy" stock at the site-product level.

In addition to the space and inventory features, general site cost and CO2 consumption features are available:

• Define startup costs and fixed CO2 consumption for sites at the period level.

• Define variable costs and CO2 consumption at the site level.

A set of new input tables provides the means for defining the spaces per site and assigning products that can utilize the space. Please note that at this time, groups are not supported for the Space column in the space assignments tables. Additional columns in the existing sites tables enable you to constrain spaces at the site level, while columns in the inventory policies tables provide a way to define obsolete/unhealthy inventory. New output tables and additional columns in existing output tables provide thorough reporting including cost and CO2 data, space utilization and expansion, and inventory metrics.

Driver scheduling in Transportation Optimization

Once you have run Transportation Optimization to produce routes, you can use driver scheduling to assign a sequence of routes to specific drivers, minimizing costs within the applicable constraints. Drivers are defined using driver classes, which determine the equipment types the driver supports, the scheduling constraints for the driver, such as maximum duty time per shift and maximum distance per driver, and the cost associated with the scheduling of the specific driver.

This feature includes new input tables:

• Drivers - Use this table to create records for each driver class. Apply constraints to limit conditions such as the allowable equipment types, number of routes, distance and working hours for the driver. You can also define fixed and variable costs that are incurred for this driver class.

• Routes - Use this table to identify the existing routes to which you want drivers assigned. The routes are those returned by the Transportation Optimization solver.

You can review the driver scheduling results in the following new output tables:

• Driver Schedule - This table displays the driver assignment per route, along with details such as the equipment used and the total route distance.

• Driver Scheduling Summary - This table provides a high-level summary of the number of scheduled and unscheduled routes, with the total cost, number of drivers and other metrics.

• Driver Summary - This table provides metrics per driver class, such as the number of routes assigned, total cost and total distance.

• Unscheduled Routes - This table identifies routes that could not be scheduled with a specific driver.

To run driver scheduling, select "Transportation Optimization" as the Technology and "Driver Scheduling" as the Problem Type on the Launch Pad.

Scenario item enhancements

You can now create and edit filters from within scenario items. These filters will be available in the input tables for which they were defined as well as in scenario items that use the specific table.

The field where you define the value for your scenario item now reflects the type of column selected. For example, if the column supports domain values, such as the groups, filters and individual values, these are available for selection in a dropdown list. Other supported column types include datetime (date picker is provided), boolean (Yes/No values only), integer and double (correctly formatted numbers only).

Model expansion

You can create a new model based on the expansion of any scenario in the model you select. You can use the expanded model to verify that your groups and scenario items are defined and working correctly. Model expansion does the following:

• Creates all individual records based on grouped records. For example, if your Transportation Policies were defined with a group for the Destination Name, the expanded model will have one Transportation Policies record for each member of the group.
• Applies the scenario items for the selected scenario. For example, if the scenario you select to expand excludes one or more sites, those sites (and any records that depended on those sites) will not be in the expanded model.
• Applies input pipes that use internal tables as data sources and populates records with the input pipe data. For example, if you have defined an input pipe to populate the Unit Sourcing Cost in Site Sourcing Policies, the expanded model with have the values populated in that column (rather than the input pipe name).

You can select Model Expansion from the Model Actions menu when you have an open model, or select a model and click Expand on the Modeler landing page.

NO-IO conversion update

NO-IO conversion has been updated to remove dependence on macro actions. This change improves performance and stability.

Configuration tables for solvers

Models now include configuration tables for the Network Optimization, Inventory Optimization and Transportation Optimization solvers: Config_NO, Config_IO, and Config_TO. These tables are used to set optional solver parameters and each is populated with a default set of parameters. To use the parameters when solving, set the Status to "Include" and adjust the Parameter Value as needed. Coupa may provide additional parameters in the future.

Additional Network Optimization output columns

The following columns have been added to Network Optimization output tables:

• Financial Summary > Tax Cost - The total cost from tax, calculated as: Period End Refundable Tax Balance + Non-Refundable Tax Credit.

• Product Summary > Intransit Inventory Holding Cost - The cost from units considered as inventory due to their inaccessibility during transportation.