PACT Guide

Join the PACT Network

To simplify the journey, we have developed detailed step-by-step guidance for you to become a PACT Conformant Solution:

Step 1/5

Review documentation

Please review all key technical documents listed on:

  1. PACT Technical Specifications & supporting materials
    Access all resources that will help build the technical foundation for PACT Conformance
  2. PACT Network Vision Paper
    Understand the foundations of the PACT Network for enabling standardized emissions data exchange

Next step
Step 2/5

Build a solution

Build a solution as per a specific version of the PACT Technical Specifications,

Need guidance on which version to choose? Please review our V3 FAQ.

Next step
Step 3/5

Connect with PACT

Join us for a 1-hour interactive session with the PACT team! This is your chance to ask questions, explore conformance testing, and gain valuable insights to support your journey. We host these sessions on the first Tuesday of every month, so don’t miss out on the opportunity to connect, learn, and grow with us!

Please sign up here.

Which resources are helpful?
Sign up: Connect with PACT
Next step
Step 4/5

Test your Solution

Ensure your solution aligns with the PACT Technical Specifications using the PACT Conformance Tool. This free, on-demand tool allows any company to validate their implementation against PACT V2 or later,

  • Instant validation – Test your solution anytime, anywhere
  • Achieve conformance – Passing all tests earns your solution a PACT Conformant status

Start your conformance test now

For more information, review our documentation on the PACT Conformance Tool on GitHub

Which resources are helpful?
PACT Conformance ToolGitHub
Next step
Step 5/5

Upload Solution to the Website

Once your solution passes 100% of all automated tests, your solution is PACT Conformant. You can then proceed to upload content using the Solution Submission Form.‍

Please see the PACT Network for details on how your solution will be displayed.

Which resources are helpful?
Solution Submission FormPACT Network
Next step

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 using the ACT tool 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. Once a solution has passed all mandatory tests using the ACT tool then it is declared PACT Conformant

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.