Skip to main content

Scenarios in Aire

A scenario is a complete version of your project model. Change an electricity price, swap a financing structure, or rewire a block’s logic, and the whole model recalculates on that version while the base stays untouched. Put the versions side by side to read which assumptions carry the outcome. Use scenarios to compare distinct alternatives: optimistic against pessimistic conditions, storage against no storage, tax equity against project finance, the same design across candidate sites. Use Sensitivity Analysis when the question is which individual inputs matter most.

Branch or Clone

Create a scenario from the scenario panel on Project Model with New scenario, or ask Aire AI to branch the scenario you name. Then choose how the new scenario relates to the one it came from. Most scenarios should be branches. Choose a clone when a version must never change, such as the model you sent to a lender. Label groups. A label groups related scenarios in the scenario panel, for example “Q4 refinance” or “Texas site”; scenarios without one sit under “Ungrouped”. Choose Label group when creating scenarios to set up several at once under a shared label, one per candidate site or one per financing structure.

How Values Flow

A branch starts out inheriting every value from its parent. As edits land in the parent, a new vendor quote or revised financing terms, they flow through to the branch for any value you have not changed, so the branch stays current instead of drifting. The moment you change a value in the branch, that value becomes an override: it holds independently and no longer tracks the parent. Everything you have not touched keeps inheriting. Change one assumption and trust that the rest of the model is still up to date. Land a change from a branch into the parent and every other branch inheriting that value picks it up, so scenarios stay in step instead of drifting apart.

Comparing Scenarios

Select scenarios in the scenario panel to put them side by side on Project Model, up to three at once, across every block and term. Or ask Aire AI to compare two scenarios and name the inputs behind the difference. The differences surface on their own, inputs and the outputs they moved together, so you read where the model diverged instead of hunting for it cell by cell.
  • Override or inherited. Each compared value is marked as an override or an inherited value, so it is clear what is driving a difference
  • Structural differences. A term that exists only in the compared scenario appears under its parent block
  • Common units. Cells with mismatched units are projected into a common unit before the variance is calculated
  • Live. Compare columns refresh when a teammate edits a compared scenario, without a reload
Tag a term with pin and it sits at the top of Project Model as a KPI card, compared across the selected scenarios. The Project Overview dashboard shows the same KPIs and charts across scenarios for the project as a whole. You always compare against the current base, not a copy that has drifted out of date, so the comparison stays honest as the model moves.

Landing Changes from a Branch

When a branch holds changes worth keeping, merge it into a target version rather than re-entering the values by hand.
  • Preview before anything is written. Choose the target and Aire lists the changed terms first
  • Take some changes, leave others. Deselect any row, and add a note to one change or to the whole set
  • Review a large set without scrolling it. Filter by change type, search for a term or block, read the changes block by block, and accept or reject many rows at once. A formula change shows what was edited, and a code block shows its configuration change
  • One new version on the target. The merge writes a single version with its own provenance, so Project History shows where the values came from
  • Downstream terms recalculate. Only the inputs you selected are sent; everything downstream recomputes on the target
If someone changes the target while your merge is open, Aire holds the merge and shows you the current version before writing anything. You can also ask Aire AI to merge a branch; it opens the same review.

Detaching a Branch

If a branch should become independent, use Detach from parent. Detaching resolves the branch’s current values into a standalone version and removes the parent link. From then on it behaves like a clone.

Who Can Branch

Anyone with edit access can create scenarios, override values, compare, and merge. Viewers can review scenarios and comparisons but cannot create or edit. Protected scenarios take edits only from the editors listed on them. See Roles & Permissions.

Building Good Scenarios

  • Pair assumptions that belong together. An optimistic case pairs high revenue with favorable costs; a pessimistic case pairs the reverse. Avoid combinations like high demand with low prices unless you are testing that hypothesis
  • Make them materially different. Two scenarios that differ by one minor input will not inform a decision
  • Keep the set small. Three to five scenarios compare well: base, optimistic, pessimistic, and one or two design or financing alternatives. To test many input combinations systematically, use Sensitivity Analysis

Reading the Results

  • Return thresholds. If only the optimistic scenario clears your hurdle rate, the project carries high risk
  • Outcome range. A narrow spread between optimistic and pessimistic points to resilient returns; a wide spread means the result rides on assumptions worth controlling or hedging
  • Downside. If the pessimistic scenario still delivers acceptable returns, the project has a margin of safety
  • Alternatives. Choose the design, technology, or capital structure on risk-adjusted returns across the cases, not on the base case alone
Site selection is a good example. A solar installation in New Mexico may generate far more than one in Minnesota, but if PPA prices are higher and land costs lower in the less productive market, the economics can favor it. Scenarios make that trade-off concrete and comparable.