Products in the same family often share the same materials, processes, and calculation methodology while differing in only a handful of parameters.

Consider a manufacturer assessing the same product across several facilities. The underlying model may remain consistent, while electricity sources, material quantities, recycled content, transportation distances, or production yields vary by location. Supporting each facility by duplicating the entire model creates extra maintenance work and increases the risk that related models drift apart.

Model Variants provides a simpler way to manage these configurations from one maintained model.

Keep one shared Baseline

Every model begins with a Baseline: the common structure and parameter values shared by its configurations.

Modelers can then create named Variants that store only the parameter values that differ from the Baseline. In the multi-facility example, each facility can have its own named Variant with its specific operating data while continuing to use the same underlying model structure and methodology.

When common values change, each Variant continues to inherit them except where it has an explicit override. Teams can update shared modeling logic once while preserving the differences that make each configuration unique.

Work with Variants throughout CarbonGraph

The selected Variant follows the CarbonGraph modeling and calculation workflow. You can:

• Switch between the Baseline and named Variants in the model and dashboard.

• Edit one Variant or manage parameter values across several Variants.

• Calculate environmental impacts using the selected configuration.

• Use a Variant as the starting point for scenario and uncertainty analysis.

• Export results for a specific model version and Variant.

• Select a committed model version and Variant when using it in a linked model system.

• Preserve Variants when committing a new model version.

This makes it possible to maintain a reviewed model once and reuse it across many products, facilities, or reporting configurations without giving up traceability.

Variants and scenarios serve different purposes

A Variant represents a named configuration that should be saved, reused, shared with everyone who can access the model, and preserved through versioning.

A scenario represents a temporary “what if?” analysis. It starts from the selected Baseline or Variant and explores additional changes without replacing the underlying configuration.

Keeping these concepts separate lets teams maintain authoritative product configurations while still exploring alternatives freely.

Built for scalable LCA and EPD programs

Model Variants is particularly useful for multi-product, multi-facility, and template-based LCA programs. Teams can maintain one common modeling foundation while producing results for the configurations needed by analysts, reviewers, and reporting workflows.

The result is less duplication, clearer traceability, and a more maintainable path from a shared model to product-specific environmental results.

Get started

Open a model and use the Variant controls to create a named configuration from the Baseline or an existing Variant. Add the parameter overrides that make the configuration unique, calculate its results, and switch back to the Baseline at any time.

Model Variants is now available to all CarbonGraph customers.