PACT Network

An open and global network of interoperable solutions

Explore PACT Conformant Solutions to measure and manage your Scope 3 emissions

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
 · Battery
 · Animal Feed
 · Metals and Mining
 · Automotive
 · Logistics
 · IT
 · Pharma
 · Chemicals
 · Manufacturing
 · Construction
 · Textile
 · Food
 · Consumer Goods
 · Cross-industry
For Technology Providers

Connect your solution to PACT Network

PACT Network establishes an open and global network of interoperable solutions for the secure peer-to-peer exchange of accurate, primary and verified product emissions data - across all industries and value chains
Resources

Quick access to resources to support you on your PCF journey

Resources

CO2 Visualization Framework

Read more
 

CO2 Visualization Framework

Read more +
Resources

The Product Carbon Footprint Guideline for the Chemical Industry

Read more
 

The Product Carbon Footprint Guideline for the Chemical Industry

Read more +
Resources

Aluminium Carbon Footprint Methodology

Read more
 

Aluminium Carbon Footprint Methodology

Read more +
Resources

Steel GHG Emissions Reporting Guidance

Read more
 

Steel GHG Emissions Reporting Guidance

Read more +
Resources

Aluminum GHG Emissions Reporting Guidance

Read more
 

Aluminum GHG Emissions Reporting Guidance

Read more +
Resources

Global Feed LCA Institute (GFLI) methodology and project guidelines

Read more
 

Global Feed LCA Institute (GFLI) methodology and project guidelines

Read more +
Resources

Navigating your Tech Options: How to leverage technology to accelerate your value chain transparency journey

Read more
 

Navigating your Tech Options: How to leverage technology to accelerate your value chain transparency journey

Read more +
Resources

Methodological guidance for the environmental assessment of aluminium intermediate and semi-finished products

Read more
 

Methodological guidance for the environmental assessment of aluminium intermediate and semi-finished products

Read more +
Resources

The Carbon Footprint of Platinum Group Metals

Read more
 

The Carbon Footprint of Platinum Group Metals

Read more +
Resources

PCF Guide: Follow the example company 'Chocolate Corp'

Read more
 

PCF Guide: Follow the example company 'Chocolate Corp'

Read more +
Resources

PACT Network Vision Paper: Enabling standardized emissions data exchange

Read more
 

PACT Network Vision Paper: Enabling standardized emissions data exchange

Read more +
Resources

iLEAP: Logistics Emissions Data Model Extension based on ISO14083 and the GLEC Framework.

Read more
 

iLEAP: Logistics Emissions Data Model Extension based on ISO14083 and the GLEC Framework.

Read more +
Resources

RMI Steel Extension: A data model extension for sharing information emissions data in steel production.

Read more
 

RMI Steel Extension: A data model extension for sharing information emissions data in steel production.

Read more +
Resources

RMI Aluminum Extension: A data model extension for sharing information emissions data in aluminum production.

Read more
 

RMI Aluminum Extension: A data model extension for sharing information emissions data in aluminum production.

Read more +
Resources

PACT Methodology Alignment Checklist: Assess the level of alignment your LCA process has with the PACT Methodology latest version.

Read more
 

PACT Methodology Alignment Checklist: Assess the level of alignment your LCA process has with the PACT Methodology latest version.

Read more +
Resources

PACT How-to (Download): A simple and structured introduction to PCF calculation

Read more
 

PACT How-to (Download): A simple and structured introduction to PCF calculation

Read more +
Resources

Guide: Calculate a PCF following the PACT Methodology

Read more
 

Guide: Calculate a PCF following the PACT Methodology

Read more +
Resources

Catena-X Product Carbon Footprint Rulebook

Read more
 

Catena-X Product Carbon Footprint Rulebook

Read more +
Resources

PACT Technical Specifications: How to build your solution’s API to be able to exchange interoperably with other solution in the PACT Network.

Read more
 

PACT Technical Specifications: How to build your solution’s API to be able to exchange interoperably with other solution in the PACT Network.

Read more +
Resources

PACT Methodology: Guidance for the Accounting and Exchange of Product Life Cycle Emissions

Read more
 

PACT Methodology: Guidance for the Accounting and Exchange of Product Life Cycle Emissions

Read more +
Insights

PACT’s Scope 3 Summit 2024: Key Insights on Scope 3 Emissions and the Path to Net Zero

Read more
 

PACT’s Scope 3 Summit 2024: Key Insights on Scope 3 Emissions and the Path to Net Zero

Read more +
Insights

Understanding Product Carbon Footprints (PCFs): Why Effective Measurement is Key for Your Business

Read more
 

Understanding Product Carbon Footprints (PCFs): Why Effective Measurement is Key for Your Business

Read more +
Insights

Introducing Product Carbon Footprints (PCFs): the essentials

Read more
 

Introducing Product Carbon Footprints (PCFs): the essentials

Read more +
Insights

Getting started on your journey – how to best engage your suppliers

Read more
 

Getting started on your journey – how to best engage your suppliers

Read more +
Visionary Sponsor

FAQs:

What is Conformance Testing?

Conformance testing is a voluntary process of verifying if a product or service meets specific standards or specifications. In the context of PACT, this is the process of verifying that a solution or system correctly implements the PACT Technical Specifications. By doing so, Conformance Testing verifies that a solution can exchange PCF data in an interoperable way with any other PACT Conformant Solution for the Tech Specs version being tested.​

Why conformant, not compliant?

Compliance is a legal requirement; Conformance refers to voluntary adherence to standards​​

What is a PACT Conformant Solution?

A PACT Conformant solution has completed the technical interoperability test with two independent solutions for a specific version of the PACT Technical Specifications. By passing conformance the solution can both share and receive PCF data via API​.

How do I get in touch with a respective solution?

Details of each solution can be found by clicking on a solution card. All PACT Conformant technology solutions have features listed on the respective page and you can visit their website and get in touch for a demo.

Can we invite a solution we already work with to go through PACT Conformance?

Most organizations are already partnering with a technology solution to measure and manage emissions data. We encourage all corporations to invite vendors and solutions you are working with to pursue PACT Conformance testing. This will ensure that the solution can exchange data using the PACT data model.

Why is the conformance of the PCF calculation not in scope for testing?​

Evaluating the calculation engine is significantly higher complexity than the exchange, and therefore deemed out of scope. We plan to expand conformance testing to the PCF calculation engine in the future.

Is there any cost to become PACT Conformant?

No, PACT Conformance testing is completely free. We have a peer-to-peer testing process with the community through which we test for conformance.

Does PACT provide a certification after conformance testing?

PACT does not provide any certifications for aligning with the standard. Hence, we do not use the terminology 'PACT Certified' or 'PACT Compliant' since it is not a legal requirement. We use 'PACT Conformant' to highlight voluntary adherence to the standard

Is PACT building a platform?

PACT is not building a product or a platform that stores any centralised data. PACT Technology is fundamentally an API that enable standardized emissions data exchange which is done in a peer-to-peer manner by individual host systems

What is tested during Conformance Testing?

1. Solution has implemented all mandatory aspects of a specific version of the PACT Technical Specifications​
2. Solution can both share and receive PCF data via API​
3. Two independent solutions confirm technical interoperability with your solution

What is not tested during Conformance Testing?

1. Any aspect of the calculation engine (i.e. PCF calculation according to PACT Methodology)​
2. User Interface and/or front-end user experience ​

Do I test conformance to a specific version of the Technical Specifications? Which version?​

Yes, conformance is relative to a specific version. Solutions must re-test to become conformant to major versions of the Technical Specifications (i.e. v1, v2, v3). You may only test conformance to a stable released version (not to a draft version). For the list of releases, see here​

Can a given solution retest multiple times if it doesn't pass the first time?​

Yes! We invite you to retest as you identify issues and bugs with your implementation, as this is an intended outcome of the Conformance Testing process.​

Why is the conformance of the PCF calculation not in scope for testing?​

Evaluating the calculation engine is significantly higher complexity than the exchange, and therefore deemed out of scope. We plan to expand conformance testing to the PCF calculation engine in the future.

Can I test conformance to data model extensions?​​

We do plan to extend conformance testing to Data Model Extensions ​once these become more widely available and adopted by solutions.​

Can my solution become PACT Conformant if it only receives PCFs, and doesn't also share them?​

No, currently the requirement for PACT Conformance is a given solution must be able to implement all mandatory functionality of the Technical Specifications which includes both send and receive API functionality.​ The above said, you are invited to nevertheless participate in Conformance Testing and may contribute test results for other solutions as well as evaluate (partially) your solution.

Is it possible to test with organizations that are building a solution for a different version to my organization?

No, the interoperability test needs to be conducted by solutions built on the same version. For example, a v3 solution cannot be tested with a v2.