Skip to main content

Terms in Aire

Terms are the core variables that power every model in Aire. Think of them like variables in code or named cells in Excel: they represent assumptions, calculations, constants, or outputs. Everything in the platform, from formulas and scenarios to exports, is built from terms.

What is a Term?

A term is a single, addressable component of the model. It might represent:
  • An input (e.g. electricity price)
  • A derived calculation (e.g. annual revenue = price × output)
  • A constant (e.g. inflation rate = 0.02)
  • An output (e.g. NPV, IRR, LCOE)
Terms serve as the connective tissue of the model, making logic reusable, traceable, and configurable across scenarios.

Term Metadata

Each term carries structured metadata to support clarity and automation:
  • Label – A human-readable display name
  • Unit – The physical or financial unit (e.g. %, USD/kW, tons/year)
  • Description – A plain-text explanation of the term’s meaning or intent
  • Source – A citation or reference indicating where the value came from (e.g. user input, paper, lab result, past project)
  • Owner – The person responsible for the value
  • Confidence – Low, medium, or high. Anyone who can edit the term can set it. A warning shows when the term has changed since the confidence was set, or when someone other than the owner set it
This metadata flows with the term through formulas, views, QA, and exports.

Terms Across Scenarios

A term has one value in the base scenario. When you create a new scenario, any term can carry a different value. electricity_price might be $0.10/kWh in your base and $0.14/kWh in an optimistic scenario. The term name stays the same across every scenario; only the value changes. This means you never duplicate your model to explore different assumptions. Each scenario can differ from the base in values, formulas, or structure, as much or as little as the analysis requires.

Validating a Term

A model is only as defensible as the inputs it rests on, so every term carries the evidence for its value and a record of who stands behind it.
  • Source. Where the value came from: a quote, a study, a past project, a test result. Add it when you set the value, and it travels with the term through every scenario, view, and export.
  • Owner and Confidence. The person responsible for the value, and how far they trust it: low, medium, or high. Anyone who can edit the term can set the confidence. A warning appears when the term has changed since the confidence was set, or when someone other than the owner set it, so a vetted value never changes quietly.
  • Review on Project Model. Filter the whole model by owner, by confidence, or by when a value last changed to find the inputs that still need a source or a second look.
  • Grade the model. Model Diligence evaluates a scenario against an investment diligence rubric and reports where the inputs hold up and where the gaps are.

Where Terms Live

Terms live inside blocks, modular units of logic that group related terms together. A block might represent:
  • A technical subsystem (e.g. a solar array, electrolyzer, or pipeline)
  • A financial component (e.g. loan structure, depreciation)
  • A structural section of the model (e.g. project wrap, summary)
Blocks can nest inside other blocks, allowing you to model complex systems in a modular, composable way.

How Terms Are Used

Terms are the foundation for all platform workflows:
  • Formulas use them to compute downstream logic
  • Views display them for analysis and reporting
  • Scenarios give terms different values to model distinct outcomes
  • AI tools interpret them to extract insights or flag risks
  • Exports package them for presentations, memos, or investor deliverables