Blueprints
Reusable templates that carry the environmental model of a product or process, normalised to a reference amount and applied to many entities.
Blueprints
A blueprint is a reusable template describing the environmental model of a product or process. It is defined once and applied to as many entities as needed, which is what makes it worth building: the alternative is entering the same set of data points on every site that makes the same thing.
What a blueprint carries
| Field | What it fixes |
|---|---|
| Reference amount | The unit every data point is normalised to — 1 tonne of product, 1 unit, 1 m³. Everything else in the blueprint is expressed per this amount. |
| Data points | The environmental inputs and outputs that make up the model, each with its value, unit and modelling parameters. |
| Impact model | Which model computes the result — the same choice as for a directly-entered data point. |
| Quality rating | The data quality the blueprint confers on the results it produces. |
| Visibility | Private to the organisation, or drawn from the public catalog. A public blueprint can be imported and then customised. |
How they are used
The library is browsed by folders, with favourites, and filtered by name, visibility, quality rating, project compatibility or impact model. Blueprints can be imported from CSV in bulk.
Applying one to an entity produces data points on that entity, scaled from the reference amount to the quantity actually involved. From there the assessment path is exactly the one a manually entered data point follows — a blueprint is a way of producing data points, not a separate input type, and it earns no methodological shortcut.
A blueprint can be recomputed when its model or its inputs change, and duplicated as the starting point for a variant. Deletion is blocked while it is in use — an entity depending on it would otherwise lose its inputs silently; deleted blueprints move to a Deleted state and can be restored.
Why the reference amount matters. It is the denominator of the whole template. A blueprint built per tonne and applied as if per kilogram is off by a factor of a thousand, and nothing downstream will catch it — the data points it generates look exactly like any other. Set it deliberately, and check it when importing a public blueprint.