Scenarios let you rapidly explore "what-if" questions against an existing Cosmic Frog model. Define one or more data changes (scenario items), run the scenarios, then compare outputs - all without altering your baseline input data.
Follow these five steps to run your first scenario:
A scenario defines one or more input-table changes to apply before running a solve. Common examples include:
In the context of this documentation, we mean the following with scenario and scenario item:
In other words: a scenario without any scenario items uses all the data in the input tables as is (often called Baseline); most scenarios will contain 1 or more scenario items to test certain changes as compared to a baseline.
Open the Scenarios module from the Module menu. A freshly opened module looks like this:

The Scenario drop-down (top of module) provides quick access to common actions:

Each scenario is associated with one engine. To change it, select the scenario and use the radio buttons in the central panel:

Right-click an existing scenario or the Scenarios folder and choose New Scenario, or use the New Scenario option from the Scenario drop-down menu. Enter a name when prompted:

Select the target scenario, then right-click → New Item (or use the Scenario drop-down). Name the item - its configuration panel opens automatically:

After selecting the table, specify the change in the Actions field. Intelli-type suggests column names as you type:

Once the column to change has been typed in, we can set its new value. In our example we want to set the value of the status column to Exclude:

Intelli-type also validates syntax. Incorrect quote style (need to use single quotes, not double quotes):

Unrecognized column name:

By default, a scenario item's action applies to every record in the selected table. Add a filter to restrict which records are changed. Two methods are available:
If Named Filters exist for the selected table, you can apply one directly to the scenario item:

After selecting a filter, the Filter Grid Preview updates to show exactly which records will be affected:

Use the Condition Builder when no applicable Named Filter exists, or for ad hoc conditions:

When multiple items modify the same column in the same table, they execute top-to-bottom. Order matters. Consider the following 2 scenarios where both scenario items are applied to the Quantity column in the Customer Demand table:

A single scenario item can be shared across multiple scenarios. The Item Assignments panel (right side) appears automatically when an item is selected:

Switch to the Item Information tab on the same panel to edit the item's name or add a description:

The Scenario Assignments panel (right side) appears when a scenario is selected, showing all available items and which are assigned:

Switch to the Scenario Information tab to edit the scenario name or add a description:

The scenarios list includes several navigation and status indicators that become useful as your model grows:


Click the green Run button (top right in Cosmic Frog), select the scenario(s) to solve, and configure technology parameters. See the Running Models & Scenarios in Cosmic Frog Help Center article for full details.
Sensitivity @ Scale automates demand-quantity and transportation-cost sensitivity analysis with a single click. See the Sensitivity at Scale Scenarios Help Center article for more information.
In addition, there are three S@S-related utilities available in the Utilities module:

Select one or more scenarios or items, then right-click ? Delete or use the Delete option from the Scenario drop-down menu at the top of the module. Key behaviors to keep in mind:

Deleting removes only the two scenarios. Items used exclusively by those scenarios move to Unassigned Items; items shared with other scenarios remain untouched.

Deleting removes both selected scenarios and all 6 selected items - including from any other scenarios that use them. The one unselected item in these 2 scenarios, "Add Inventory capacity at CDCs", remains.
Use Delete Scenario Results (context menu or Scenario drop-down) to clear output data for one or more scenarios without removing the scenarios themselves:

Think through scenario naming conventions ahead of time. You can for example:
Most input tables include Status and Notes fields. A powerful scenario pattern is:
This keeps all data in the model without interfering with the Baseline.
Custom columns let you store alternative values in a table and reference them in scenario items, e.g.:
The Copy Scenarios utility (Utilities module → Copy to a Model) copies a single scenario or all scenarios from one model to another, including all items and assignments.
Ada is Optilogic's agentic AI and while chatting with her she can create new scenarios and their associated items for you. See the Getting Started with Ada & Agentic AI article to get going with Ada.
In addition, you can also use Leapfrog for scenario and item creation, and scenario-specific data manipulation.
Like Ada, Leapfrog can create scenarios and scenario items from a plain-language description - ideal for quickly spinning up variations without manually configuring each item. See the specific section on this in the Getting Started with Leapfrog AI Help Center article.
🔧 Use Case: 2027 Demand Projections from 2026 Numbers
Model 2027 demand from 2026 quantities using a custom growth projections table. Both Ada and Leapfrog can be utilized to set this up, so no external tool needs to be used. In Leapfrog, you can achieve the goal for example in following 4 steps:
Using Ada, you will be able to use 1 prompt explaining the goal while attaching the growth projections table. For example: "The attached model contains 2026 demand in the Customer Demand table, copy this entire set and paste as a new set with Status set to Exclude and Notes field set to 2027 scenarios. In the new 2027 set, multiply the demand quantities with the growth projection numbers in the attached file. Then create a scenario that does not use the 2026 demand, but the 2027 demand instead."
Happy scenario modeling! As always, please contact our Support team on support@optilogic.com for any questions or feedback.
Scenarios let you rapidly explore "what-if" questions against an existing Cosmic Frog model. Define one or more data changes (scenario items), run the scenarios, then compare outputs - all without altering your baseline input data.
Follow these five steps to run your first scenario:
A scenario defines one or more input-table changes to apply before running a solve. Common examples include:
In the context of this documentation, we mean the following with scenario and scenario item:
In other words: a scenario without any scenario items uses all the data in the input tables as is (often called Baseline); most scenarios will contain 1 or more scenario items to test certain changes as compared to a baseline.
Open the Scenarios module from the Module menu. A freshly opened module looks like this:

The Scenario drop-down (top of module) provides quick access to common actions:

Each scenario is associated with one engine. To change it, select the scenario and use the radio buttons in the central panel:

Right-click an existing scenario or the Scenarios folder and choose New Scenario, or use the New Scenario option from the Scenario drop-down menu. Enter a name when prompted:

Select the target scenario, then right-click → New Item (or use the Scenario drop-down). Name the item - its configuration panel opens automatically:

After selecting the table, specify the change in the Actions field. Intelli-type suggests column names as you type:

Once the column to change has been typed in, we can set its new value. In our example we want to set the value of the status column to Exclude:

Intelli-type also validates syntax. Incorrect quote style (need to use single quotes, not double quotes):

Unrecognized column name:

By default, a scenario item's action applies to every record in the selected table. Add a filter to restrict which records are changed. Two methods are available:
If Named Filters exist for the selected table, you can apply one directly to the scenario item:

After selecting a filter, the Filter Grid Preview updates to show exactly which records will be affected:

Use the Condition Builder when no applicable Named Filter exists, or for ad hoc conditions:

When multiple items modify the same column in the same table, they execute top-to-bottom. Order matters. Consider the following 2 scenarios where both scenario items are applied to the Quantity column in the Customer Demand table:

A single scenario item can be shared across multiple scenarios. The Item Assignments panel (right side) appears automatically when an item is selected:

Switch to the Item Information tab on the same panel to edit the item's name or add a description:

The Scenario Assignments panel (right side) appears when a scenario is selected, showing all available items and which are assigned:

Switch to the Scenario Information tab to edit the scenario name or add a description:

The scenarios list includes several navigation and status indicators that become useful as your model grows:


Click the green Run button (top right in Cosmic Frog), select the scenario(s) to solve, and configure technology parameters. See the Running Models & Scenarios in Cosmic Frog Help Center article for full details.
Sensitivity @ Scale automates demand-quantity and transportation-cost sensitivity analysis with a single click. See the Sensitivity at Scale Scenarios Help Center article for more information.
In addition, there are three S@S-related utilities available in the Utilities module:

Select one or more scenarios or items, then right-click ? Delete or use the Delete option from the Scenario drop-down menu at the top of the module. Key behaviors to keep in mind:

Deleting removes only the two scenarios. Items used exclusively by those scenarios move to Unassigned Items; items shared with other scenarios remain untouched.

Deleting removes both selected scenarios and all 6 selected items - including from any other scenarios that use them. The one unselected item in these 2 scenarios, "Add Inventory capacity at CDCs", remains.
Use Delete Scenario Results (context menu or Scenario drop-down) to clear output data for one or more scenarios without removing the scenarios themselves:

Think through scenario naming conventions ahead of time. You can for example:
Most input tables include Status and Notes fields. A powerful scenario pattern is:
This keeps all data in the model without interfering with the Baseline.
Custom columns let you store alternative values in a table and reference them in scenario items, e.g.:
The Copy Scenarios utility (Utilities module → Copy to a Model) copies a single scenario or all scenarios from one model to another, including all items and assignments.
Ada is Optilogic's agentic AI and while chatting with her she can create new scenarios and their associated items for you. See the Getting Started with Ada & Agentic AI article to get going with Ada.
In addition, you can also use Leapfrog for scenario and item creation, and scenario-specific data manipulation.
Like Ada, Leapfrog can create scenarios and scenario items from a plain-language description - ideal for quickly spinning up variations without manually configuring each item. See the specific section on this in the Getting Started with Leapfrog AI Help Center article.
🔧 Use Case: 2027 Demand Projections from 2026 Numbers
Model 2027 demand from 2026 quantities using a custom growth projections table. Both Ada and Leapfrog can be utilized to set this up, so no external tool needs to be used. In Leapfrog, you can achieve the goal for example in following 4 steps:
Using Ada, you will be able to use 1 prompt explaining the goal while attaching the growth projections table. For example: "The attached model contains 2026 demand in the Customer Demand table, copy this entire set and paste as a new set with Status set to Exclude and Notes field set to 2027 scenarios. In the new 2027 set, multiply the demand quantities with the growth projection numbers in the attached file. Then create a scenario that does not use the 2026 demand, but the 2027 demand instead."
Happy scenario modeling! As always, please contact our Support team on support@optilogic.com for any questions or feedback.