When EPDs, life cycle assessments and PCFs are needed for many products and variants, the individual project turns into a recurring data and calculation process. We structure product, production and environmental data as well as LCA models so that they can be used for recurring calculations and different environmental requirements. The data basis can be used several times; EPD, PCF and other declarations continue to be prepared according to their respective technical rules.
We structure product structures, production and environmental data as well as LCA models so that they can be used for recurring calculations and different environmental requirements. The data basis can be used several times; EPD, PCF and other declarations continue to be prepared according to their respective technical rules.
Many manufacturers start with a single EPD. As soon as further products, variants or requirements are added, isolated individual calculation is often no longer sufficient.
Not every product variant necessarily has to be declared in its own EPD. Depending on product structure, target market, PCR and programme rules, several products can be grouped via different EPD types. The underlying calculation can be based on reusable or parameterised LCA models.
How products and variants can be declared in EPDs depends, among other things, on product portfolio, PCR, programme requirements and the intended significance.
Which type is suitable and permissible depends on the product portfolio, target market, PCR and the rules of the respective programme operator.
Regardless of the EPD type chosen, the calculation can be based on a reusable or parameterised LCA model.
Whether a manual, hybrid or software-supported approach is economically sensible depends on portfolio, update frequency and data situation.
Product, material and supplier data are rarely in one place. We capture them in a structured way, check quality and gaps and define which data are permanently required for recurring calculations.
Whether a direct system integration makes economic sense or a structured data export is sufficient is clarified in the project.
Expert LCA work and data modelling from a single source. We define the degree of automation only once portfolio and data situation are understood.
Only once portfolio, required declarations, target markets, programme rules and update frequency have been clarified can it be decided which implementation route makes economic sense: manual, hybrid or software-supported.
The larger and more dynamic the portfolio and the more frequently EPDs or other declarations need to be updated, the more important structured data, reusable calculation logic and efficient processes become.
Determine the right EPD route →Which route makes economic sense depends not only on the number of products but also on variant logic, data situation, update frequency and the requirements of the target markets.
For larger or dynamic product portfolios, software-supported solutions can make recurring data, calculation and declaration processes more efficient. Which solution makes sense depends on data situation, variant logic and update frequency.
Briefly describe your portfolio, variants and requirements. We assess whether project work, a repeatable process or a software-supported solution makes economic sense.
