Skip to main content

Models

Anything from an early-stage screening model to a detailed techno-economic analysis or a full project finance model. The Project Success team works with you to ingest it with its terms, formulas, and dependencies intact, and checks it against the original before it goes live. See Importing Models.
Yes. Export any scenario to Excel from Project Model, or several scenarios into one workbook. Viewers can export as well as Editors and Admins. See Exporting.
Yes, through a code block. Package the function as a container, map its inputs to terms, and its outputs come back as terms that the rest of the model references. It re-runs when its inputs change. See Code Blocks.
Aire flags it on the term. Every term carries a unit, and every formula is checked for unit consistency, so adding MW to MWh or applying /kWwhere/kW where /MW is expected surfaces as an error instead of a plausible wrong number. Aire never converts silently. See Units.
Give the term a source, and set an owner and a confidence level. A warning appears when the value changes after the confidence was set. Filter Project Model by owner or confidence to review a model before it goes to a counterparty. See Validating a Term.

Scenarios and Analysis

Use scenarios to compare distinct alternatives, such as a storage design against no storage or tax equity against project finance. Use sensitivity analysis to find which individual inputs move an output most, or to put a distribution on uncertain inputs with Monte Carlo. See Scenario Analysis and Sensitivity Analysis.
A branch starts as a copy and keeps picking up updates to the original, except for the values you change. A clone is a one-off copy that later changes never reach, useful when a version must stay exactly as it was. See Branch or Clone.
Yes. List editors on the scenario and only they can change it, whether directly, through Aire AI, by merging a branch, or by running a code block. Everyone else keeps working in their own branches. See Protected Scenarios.
Yes. Project History records every change to values, formulas, units, sources, and structure, with who made it and when, separately for each scenario. See Project History.

Aire AI and Your Data

Yes, in the scenario you name, and every edit passes the same validation and permissions as one you make by hand. It never edits the project base directly: changes to the base go on a working branch for you to review and land. See Aire AI.
No. Aire AI runs on enterprise APIs under terms that exclude training on customer data, and your organization’s data is never visible to another organization. See Security & Data Handling.
Not today. Roles apply across every project in an organization. Use separate organizations for teams that need separate boundaries, and protect scenarios to control who can change them. See Roles & Permissions.