Emission Footprint Calculation via API Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Emission footprints are not integrated across certain software applications or computer systems, limiting their consumption and utilization for environmental impact assessments and optimization.

Innovation Solution

A computer system and method that calculates emission footprints per product, material, and activity by obtaining product data and emission factor data, and provides these footprints via an application programming interface or as published events for consumption by other software applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If emission footprints are calculated and stored in isolated systems, then calculation accuracy is maintained, but integration and consumption across software applications is limited

Engineering Contradiction:
Improveintegration capabilityVSAvoidemission footprint accessibility
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The emission footprint system is segmented into independent calculable units (product-level, material-level, activity-level footprints) that can be calculated and stored separately, then integrated through standardized interfaces. This allows each component to maintain calculation accuracy while enabling flexible integration across different software applications through the API and event mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary layer consisting of standardized application programming interfaces (APIs) and event publishing mechanisms is introduced between the emission footprint calculation system and consuming software applications. This intermediary enables seamless integration and information exchange without compromising the integrity or accuracy of the emission footprint calculations, allowing multiple applications to consume footprint data in various formats and contexts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If emission footprints are integrated across multiple software applications, then consumption and utilization improve, but system complexity increases

Engineering Contradiction:
Improveemission footprint consumptionVSAvoidsystem integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The emission footprint system implements universal interfaces and standardized data structures that can be consumed by multiple different software applications (ERP, procurement, product planning systems) through a common API framework. This multi-functionality allows the same emission footprint calculation engine to serve diverse applications without requiring separate integration implementations for each, thereby improving consumption while controlling complexity through standardization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system allows emission footprint data to be represented and exchanged in various parameter formats and granularities (product-level aggregates, material-level breakdowns, activity-level details) depending on the specific needs of consuming applications. This parameter flexibility enables different applications to consume the same underlying footprint data in the format most suitable for their purposes, reducing integration complexity while maximizing utility.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If detailed product data and emission factor data are collected, then calculation precision improves, but data processing time increases

Engineering Contradiction:
Improveemission footprint accuracyVSAvoidcalculation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

Emission factor data is pre-collected, pre-validated, and pre-organized in a standardized database before being needed for footprint calculations. Product data structures are pre-configured with relevant emission-related attributes. This preliminary preparation ensures that when footprint calculations are performed, the system can immediately access accurate, validated data without time-consuming data gathering or validation steps during the actual calculation process, thereby maintaining precision while reducing calculation time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250045771A1Emission footprint calculation and consumption
Publication Date: 2025.02.06 SAP SE
  • US20250045771A1 patent drawing
  • US20250045771A1 patent drawing
  • US20250045771A1 patent drawing

AI summary

Emission footprints can be calculated and provided for consumption by software applications. To do this, product data including a quantity of a product, components of the product, and activities for the product are obtained. Emission factor data for the components indicating a carbon dioxide impact of the components per unit are obtained. One or more emissions footprints are calculated per product, per material, and per activity based on a time period, the quantity, the components, the activities, and the emission factor data. Each of the emissions footprints indicates an amount of carbon dioxide per unit for a corresponding product, material, or activity. The calculated emissions footprints for the time period are provided via an application programming interface or as a published event.