Not every sector can be managed with the same data logic. Even processes on production lines may require different methodologies. Therefore, attention should be given to process-based infrastructure rather than ready-made packages. Work based on generic packages can create irreversible consequences during an independent verifier’s site visit. Even within the same product family, process route, energy structure, auxiliary inputs and evidence depth can create different risks. That is why we build a sector-based but controlled working model that does not expose internal company know-how.
Aluminium
In the aluminium sector, most indirect emissions are not included in CBAM emissions calculations, but one critical point must be considered. If production route, auxiliary processes, metal flow and precursor inputs are not read together, files that appear technically prepared may not be commercially convincing. Even if indirect emissions are not included in the emissions calculation, they should be calculated, filed with evidence documents and presented to the independent verifier.
When the primary/secondary structure, melting logic, product-line relationship and data defensibility are correctly structured, trust on the importer side is built much faster.
- Product-line-based data flow
- Consolidating energy and process data into a single-file logic
- Controlled technical explanation that can be shared with the customer
Iron and Steel
In iron and steel, CBAM cannot be managed without understanding the production route. Sinter, pig iron, DRI, crude steel, semi-finished and downstream products do not carry the same risk profile.
In this sector, a small data-structure error can affect multiple product families. The real need is to establish a clear and traceable link between process boundary and product declaration.
- Clarifying precursor material and process flow
- Structuring the fuel/process distinction
- Technical response infrastructure for importer questions
Cement
In cement, the emissions story is often read not from the product name, but from composition and production setup. Therefore, the product, clinker relationship and process boundary must speak the same logic.
A common issue in the field is that data exists, but does not come together in the same file with a CBAM perspective. We match composition logic with evidence structure to strengthen the commercial defensibility of the report.
- Clarifying the product-clinker relationship
- Traceability of energy and process data
- Shareable but controlled methodology language
Fertilisers
In fertilisers, final product tonnage alone is not enough. Product composition, process route, intermediate products and energy relationship determine file integrity.
Most companies have production, laboratory and energy data; however, these data do not meet on the same projection under CBAM declaration logic. The value we create is precisely closing this technical gap.
- Structuring composition and process logic in the same file
- Organizing precursor data flow
- Preparation for customer questionnaires
Hydrogen
In hydrogen, marketing language and regulatory language are often not the same. A “low-carbon” claim alone is not enough; production route, energy data, emissions boundary and evidence structure are assessed together.
For this reason, a strong hydrogen file comes not from ambitious wording, but from traceable and consistent data flow.
- Readiness for actual data use
- Early establishment of evidence architecture
- Technical file that builds trust with the importer
Electricity
Electricity requires a different response from other sectors. Here, not only production but also cross-border flow, suitable methodology and document integrity become critical.
The approach of “we have production data” is often not enough. On the electricity side, technical suitability and document suitability must be managed together.
- Clarifying suitable data boundaries
- Strengthening document and evidence integrity
- Defensible file structure for the importer
English
Eesti
Türkçe