Serbian manufacturers preparing for growing carbon-data requirements from European customers need to connect six core factory systems to establish traceable emissions records, from energy consumption and material sourcing to production output and final product calculations.
The systems include utility metering, production control, enterprise resource planning (ERP), material genealogy, contractual documentation, and emissions calculation and reporting. Their integration allows manufacturers to explain how energy and materials are transformed into finished products and generate consistent evidence for the EU Carbon Border Adjustment Mechanism (CBAM), corporate greenhouse-gas reporting and product carbon footprints. The main engineering challenge is often not a shortage of data, but inconsistent identifiers, timestamps and reporting boundaries across systems already used by different departments.
Utility Metering and Production Data Establish the Baseline
The first component is the electrical and utility metering hierarchy, covering fiscal import meters, on-site generation, major process loads, fuels, heat, steam and other relevant energy streams. Meter identifiers, transformer ratios, units, timestamps and maintenance status must be controlled.
A 15-minute measurement interval can serve as a useful engineering standard where equipment supports it. CBAM electricity rules can require reconciliation within periods of one hour or less for specific claims based on actual values.
The second component is production control. SCADA systems, manufacturing execution software and plant historians can record equipment operating periods, product runs and production volumes. Connecting these records to energy consumption allows manufacturers to allocate emissions using actual operating data rather than relying exclusively on annual averages. Where digital production systems are unavailable, controlled shift logs and machine-hour records can provide an alternative basis for allocation.
ERP and Material Genealogy Connect Emissions to Products
The third system is the ERP environment, which contains purchasing, inventory, production orders, sales and financial records. Its role is to connect emissions calculations with the factory’s commercial and production activities.
Master data must align across departments. A product code used by sales should correspond to the production route defined by engineering and, where relevant, the Combined Nomenclature (CN) code used for customs. Material suppliers and individual lots must also link to the emissions information used in calculations.
The fourth component is material genealogy, maintained through a warehouse-management system, batch database or controlled ledger. It preserves the chain from the original supplier and material grade through receipt, production consumption, scrap and finished output. For steel and aluminium processors, this traceability can have a greater influence on reported product emissions than the factory’s own electricity consumption. If materials are pooled without preserving their origins, manufacturers may have to rely on average values or default emissions factors.
Contracts Determine Which Evidence Can Support Carbon Claims
The fifth system covers contractual evidence, including electricity supply agreements, power purchase agreements (PPAs), guarantees of origin, precursor-data clauses and customer reporting obligations.
These documents determine whether physical production and energy data can support a particular emissions claim. Relevant contract information, eligibility conditions, reporting periods and evidence deadlines should therefore be accessible to the monitoring, reporting and verification process rather than remain confined to legal departments. The sixth system is the emissions calculation and reporting layer. It should use validated source data without overwriting original records and apply version-controlled methodologies for CBAM, corporate greenhouse-gas reporting and product footprints.
Different reporting outputs can draw on the same evidence while retaining their own boundaries and calculation rules. The system must preserve emissions factors, allocation methods, manual adjustments and report versions so that previously issued results can be reproduced.
Data Integration Requires Consistent Identifiers and Controls
Connecting the six systems does not require a single software provider. Manufacturers can link existing platforms through interfaces and a controlled data model that assigns unique identifiers to meters, products, materials and suppliers. This requires both technical integration and consistent definitions. Departments must use the same identifiers and understand product batches, production periods and electricity sources in the same way.
A further requirement is identity management, which ensures that a generator, supplier, meter or product is recognised consistently across databases. Duplicate supplier records, renamed meters and inconsistent units can introduce reconciliation errors. Assigning responsibility for maintaining master data is therefore an important part of carbon digitalisation.
Cybersecurity and change management must also be incorporated into the architecture. Automated data flows can affect regulatory filings and commercial reports, making access controls, backups and software-change procedures necessary. Any new meter, supplier or production route should trigger a review of the monitoring plan and the associated calculation mappings.
Reporting Architecture Must Support Verification and Continuity
Manufacturers should design systems to provide structured data exports for EU customers and independent verifiers. Controlled data packages should contain timestamps, units and references without requiring external parties to access operational technology systems directly.
A controlled calculation catalogue can further standardise reporting. Each metric should have an assigned owner, defined input fields, documented emissions-factor sources, an allocation method and an output unit. When a customer requests a new product footprint, the factory can determine whether an existing calculation is suitable or whether a different methodology is required.
Business continuity is another consideration. If an interface fails, the factory should be able to identify affected reports and determine which approved fallback data can be used. A failed SCADA connection, for example, should not require the entire year’s records to be reconstructed from invoices. Redundancy, backups and documented manual-recovery procedures can help preserve reporting continuity when individual systems or interfaces become unavailable. For Serbian exporters, integrating these systems provides a common evidence base for different EU customer requests. It can reduce repeated data preparation, expose missing information earlier and support independent verification through traceable production and emissions records.
Elevated by CBAM.Clarion.Engineer
