Introduction

As iLEAP works toward becoming the standard for the exchange of logistics emissions data, it is crucial to ensure interoperability across implementations. To support this goal, we're launching the iLEAP Approval process that will test and officially assert conformance, strengthening the entire ecosystem. This process will be an add-on to the existing SFC Certification, aiming to fully integrate both processes in the long run.

The kick-start of iLEAP Approval is divided into three phases:

1. Pilot Phase (complete): We ran two pilot approvals in Q1 with SFC Certified tool providers selected from a shortlist.
2. Rollout Phase (ongoing): Based on the insights from the Pilot Phase, we are rolling out the iLEAP Certification process with the three remaining tool providers in the shortlist. We aim to complete the rollout phase by the end of Q3 2026.
3. Full Operations (planned): Based on the insights from the Rollout Phase, we will make iLEAP Approval available to all SFC Certified partners.

Approval Process (Rollout Phase)

Pre-requisites

• Being SFC Certified (i.e., having a valid, less than 12 months old, SFC Certification);
• Having implemented at least iLEAP Data Transactions #1 (TCE Data Exchange) and #2 (TOC/HOC Data Exchange).

Process

• iLEAP implementations will be tested using the Automated Conformance Testing (ACT):
  • PACT-related tests, performed using the PACT Conformance Service.
  • iLEAP-related tests, documented in the Appendix C of the iLEAP Technical Specifications.
  • The test runs are performed asynchronously or during a call.
• The test results will be evaluated by the iLEAP team, leading to two possible outcomes:
  • Passed: if the success criteria are met, the tool is considered iLEAP Approved.
  • Failed: When success criteria are not met, the tool provider is given a two-week timeframe (subject to negotiation) to implement the necessary API changes and rerun the certification tests. This remediation cycle may be repeated up to two times, allowing for a maximum of three certification test runs.
    • After three failed attempts: If concerns arise about the tests or the Technical Specifications, the iLEAP team will review potential adjustments to either. Tool providers may also be offered the opportunity to retest at a later date at no additional cost.
• Two calls (30-45 minutes each) will be scheduled: one before testing begins and one after results are available.

Success Criteria

A tool provider is considered iLEAP Approved if and only if its iLEAP implementation

• Passes essential PACT tests. These are the PACT-related tests that are necessary to enable iLEAP Data Exchanges:
  • Authentication tests;
  • Action ListFootprints tests;
  • Action GetFootprint tests.
• Passes iLEAP Tests related to DT#1 and DT#2

In addition, tests related to DT#3 will be run. Passing them is optional, but recommended.