Emission Factor Matching Engine

The engine does not perform a simple one-to-one lookup. It algorithmically selects the most appropriate factor by evaluating multiple, simultaneous dimensions of a transport activity:

• Transport Mode: Distinguishes between air, road, rail, sea, and inland waterways.
• Fuel Type & Technology: Differentiates diesel, LNG, electric, and sustainable aviation fuel (SAF).
• Vehicle Specification: Accounts for gross vehicle weight, payload capacity, and Euro emission class standards.
• Operational Context: Factors in average load factor, empty running percentage, and temperature control for cold chain logistics. This granularity ensures the calculated emission accurately reflects the real-world operation, not a generic industry average.

The engine relies on a curated, version-controlled database that structures emission factors in a strict hierarchy to resolve conflicts:

1. Supplier-Specific Data: Primary factors sourced directly from a carrier's verified fuel consumption, aligned with the GLEC Framework.
2. Industry-Average Data: Default factors from recognized databases (e.g., EcoTransIT, UK DEFRA) when primary data is unavailable.
3. Modeled Defaults: Calculated factors based on vehicle physics and energy models as a last resort. The engine automatically audits and timestamps the source of every factor used, establishing carbon data provenance for every calculation.

A sophisticated engine automatically computes emissions across the full energy lifecycle, not just the tailpipe. It applies a Well-to-Wheel (WTW) methodology by summing two distinct factor sets:

• Well-to-Tank (WTT): Accounts for emissions from fuel extraction, refining, and distribution. This is critical for accurately comparing diesel with electricity or hydrogen.
• Tank-to-Wheel (TTW): Accounts for emissions from the combustion or operation of the vehicle itself. This prevents greenwashing by exposing the upstream carbon cost of ostensibly 'zero-emission' vehicles, enabling a true lifecycle assessment.

The engine abstracts away the complexity of disparate data inputs by automatically normalizing all activity data to a standard unit before applying a factor. It handles conversions such as:

• Distance: Kilometers to miles.
• Weight: Kilograms to short tons.
• Volume: Cubic meters to TEU (Twenty-foot Equivalent Unit) for ocean freight.
• Composite Units: Calculating ton-kilometers from separate weight and distance inputs. This ensures that a factor expressed in kg CO2e per ton-km can be correctly applied to a shipment recorded in lbs and miles, eliminating a major source of manual calculation error.

For every calculated emission value, the engine generates a complete, immutable audit trail that links the output back to its source data. This trace includes:

• The unique ID and version of the specific emission factor used.
• The source database (e.g., supplier-reported vs. industry-default).
• The raw activity data input (distance, weight, mode).
• The intermediate normalization and calculation steps. This deterministic record is essential for ISO 14083 compliance and provides the defensibility required for external assurance and Carbon Disclosure Project (CDP) reporting.

The engine is designed as a stateless, API-first microservice to embed carbon intelligence directly into operational workflows. It enables real-time calculations for:

• Carbon-Aware Tender Engines: Evaluating the carbon cost of a freight bid before acceptance.
• Dynamic Route Optimization: Comparing the emission profile of multiple route options before dispatch.
• Order Promising Logic: Providing a carbon estimate alongside a delivery date promise at checkout. This programmatic access transforms carbon accounting from a periodic, backward-looking report into a forward-looking, operational decision-making tool.

A comprehensive life-cycle analysis method that accounts for total energy consumption and emissions from fuel production (well-to-tank) through combustion in a vehicle (tank-to-wheel). An emission factor matching engine must distinguish between these scopes when selecting factors, as a tank-to-wheel factor for diesel is fundamentally different from a well-to-wheel factor that includes extraction, refining, and distribution emissions.

A cryptographically secured, immutable record of the origin, chain of custody, and transformation history of an emission data point. For an emission factor matching engine, provenance ensures:

• The source database version is traceable
• Any factor modifications or overrides are logged
• The selection logic is auditable for regulatory compliance
• Immutability prevents tampering with historical calculations

An accounting methodology that assigns carbon emissions to specific logistics activities based on their actual resource consumption. The emission factor matching engine serves as the calculation backbone for this approach by:

• Matching the correct factor to each discrete activity
• Enabling granular attribution of emissions to cost objects
• Supporting what-if analysis by swapping factors for alternative modes or fuels

The computational process of quantifying indirect greenhouse gas emissions in a company's value chain. Category 4 (Upstream Transportation) and Category 9 (Downstream Transportation) of Scope 3 rely heavily on accurate emission factor matching. The engine must handle:

• Primary data from actual carrier fuel consumption
• Secondary data using distance-based and spend-based factors
• Hybrid models that blend both approaches for maximum accuracy