What's new in Supply Chain Guru X

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 before solving, modeling, using with apps, or solving on the cloud. As of R41, support is ending for the following schema version, and older model schemas:

• Release R38 (schema 406000)

Changes to platform integration for older versions of Supply Chain Guru X

Starting with the May 2025 Release (R42), integration between the llama.ai platform and versions R39 and earlier of Supply Chain Guru X and Data Guru will no longer be supported. This update is part of our ongoing commitment to strengthen network security and will affect logins to llama.ai from these older versions. Integration features such as Cloud Solving and the ability to upload and download models and data from within these versions will no longer be available. Note that this change does not impact the local functionality of your desktop products or your ability to upload and download assets through a browser.

To continue using Data Guru and Supply Chain Guru X with llama.ai seamlessly, upgrade to the latest version of the desktop products.

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 flows or revenue through the sites to calculate the weighted average site 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 - This objective is based on the weighted average aggregated risk across all the facilities in the network.

• Maximum Network Risk - This objective relaxes the risk constraint defined by the Maximum Network Risk value specified in Network Optimization Options, and puts the deviation term into the objective.

• Maximum Product Risk - This objective relaxes the risk constraint defined by the Maximum Risk value specified in the Products table, and puts the deviation term into the objective.

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 step function where the first value in each pair is the gap percentage and the second is the run time (in seconds). Two sets of values are supported.

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

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

Platform support for model versions

The Supply Chain platform supports solving models with a database schema of up to 1 year old. As of August 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)

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 platform sign in feature

The process of signing into the Supply Chain platform from Supply Chain Guru X has been aligned with the standard platform sign in. From Supply Chain Guru X, you are directed to a browser tab using your default browser.

If you are already signed into the platform, you will not have to enter your credentials. If you are not already signed in, enter your credentials to sign in for both Supply Chain Guru X and the platform. Signing out from Supply Chain Guru X signs you out of both the desktop and platform products.

SQL Server 2014 Support

Microsoft will no longer be supporting SQL Server 2014 as of July 9th, 2024. In light of this, llama.ai will no longer allow uploads of SQL Server 2014 starting June 1st, 2024 and will be fully deprecated on July 5th, 2024. Additionally, any existing SQL Server 2014 databases will be migrated to SQL Server 2019 on the deprecation date of July 5th, 2024. This means if you download these databases you will receive them as SQL Server 2019. If this is problematic, you can use our APIs to extract your data. Please contact Coupa Support for questions or assistance.

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 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)

Option to avoid ferries when calculating paths

An option has been added to the Calculate Detailed Paths feature in the Transit Matrix table that has the provider avoid using ferries in the path returned to Supply Chain Guru X. Currently, the “Avoid Ferry Route Calculation If Possible” option applies specifically to the “Bing Maps” provider.

New Allocation Constraints 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.

Improved model upload process

Uploading models to the llama.ai platform has been enhanced to be more reliable, especially for larger models. The performance is generally improved compared to the previous upload process.

Improved model download process

When downloading models from the llama.ai platform to a Supply Chain Guru X project, the download model flyout accommodates a larger set of model names (the limit is now 10,000). The values are sorted alphabetically to make it easier to select the desired model for download.

Updated endpoint for RateWare XL interface

The endpoint used when calculating shipping rates using RateWare XL has been updated to use an SMC3 production host (applications.smc3.com). The calls are using a secure TLS 1.2 protocol.

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 time

The Driver Summary output table now includes a Duty Duration column displaying the total duty time for each driver.

Time-based allocated cost in shipment output

The existing allocated cost calculation in the Shipment Output and Delivered Shipments tables apportions a route’s total cost to each shipment on the route by weighting each shipment using the product of the shipment’s quantity and its travel distance on the route. This calculation method does not factor in the load and unload times of the shipments; shipments with excessively long load and unload times should be penalized and apportioned a larger share of the route’s total cost. To address this, the existing Allocated Cost column has been renamed to Distance-Based Allocated Cost. A new column, Time-Based Allocated Cost uses the product of each shipment’s quantity and its surface time (its travel time on the route combined with its load and unload time) as the shipment’s weight in the allocation cost calculation.

Start- and end-of-route service times for transportation assets

New columns in the Transportation Assets input table, Start Of Route Service Time and End Of Route Service Time, allow you to specify independent service times at the start and end of every route to account for pre-/post-route activities. These activities can be documentation, vehicle refueling, and others. Positive start-of-route and end-of-route service times are reflected in the output as positive time spans for the ‘EquipmentStart’ and ‘EquipmentEnd’ activity types in the Route Details table. They are also factored into service-time and duty-time cost calculations.

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.

Configuring SCGX to connect to eu.llama.ai

Access to the Supply Chain from Supply Chain Guru X is controlled by the SupplyChainGuru.exe.config file in the installation folder (typically C:\Program Files\Coupa\Supply Chain Guru X). By default, this file is set up to use the us.llama.ai instance. The keys needed to connect to the eu.llama.ai Supply Chain platform instance are included in the SupplyChainGuru.exe.config file. To connect to eu.llama.ai, you need to remove the comment flag from these eu.llama.ai keys:

<add key="DotComAuthenticationUri" value="https://eu.llama.ai/api/authentication/"/>
<add key="DotComUrl" value="https://eu.llama.ai" />
<add key="DotComClientId" value="b6ec1ec8-05a6-45e3-a077-96aceb837e35" />

Stamen basemaps are no longer supported

The Stamen Watercolor and Stamen Toner basemaps are no longer available on the Stamen site. They are therefore unavailable in Supply Chain Guru X maps. If you have maps that currently reference these basemaps, you can select one of the available basemaps to use instead.

End of support for the legacy Network Optimization solver

The legacy Network Optimization solver is no longer available in Supply Chain Guru X. Please contact Coupa Support with any questions.

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)

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.

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)

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.

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.

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.

Bing Road as the default basemap

When creating a new map, Bing Road is now the default basemap displayed.

Platform support for model versions

The Coupa 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)

Older models can still be uploaded to llama.ai, but must be upgraded in order to be used.

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.

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.

In prior releases, you added these tables to your model using Model Transformations. With this enhancement, the Model Transformations that were used to create these tables have been removed.

If you have an existing model that already includes the configuration tables as user defined tables:

• The tables will be recreated as standard tables and populated with the parameters as in the existing user defined tables.

• The user defined tables will be removed.

Deprecation of "Create Advanced Parameter Table" model transformations

The configuration tables generated by the three advanced parameter table model transformations are now standard tables in the model database. As a result, these transformations are no longer available under Model > Model Transformations:

• Created Advanced NO Parameter Table

• Created Advanced IO Parameter Table

• Created Advanced TO Parameter Table

Improvement for Network Optimization with large models

The Supply Chain Guru X configuration has been updated to better handle Network Optimization models with millions of records. This change will prevent cases where Network Optimization failed with an out of memory error, even when there was sufficient memory.

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.

Driver scheduling available for cloud solving

The Driver Scheduling problem type in Transportation Optimization can now be run using the Cloud solving engine.

Driver scheduling available for command line solving

The Driver Scheduling problem type in Transportation Optimization can now be run using the Supply Chain Guru X command line solver. You can run it using the 'transopt' argument with a type value of 'ds'.

Option to turn off Cost To Serve dynamic view

The View Costs button on the Cost To Serve Details output table provides access to a dynamic view of the costs produced by Cost To Serve Analysis. In some large models, the output file that populates the dynamic view is too large to import successfully. 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.

NO-IO conversion update

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

Installed component information

The list of installed components in the Help > About Coupa Supply Chain Guru window has been expanded to include both standard and legacy solver version information.