Skip to main content

About Pilots

This README describes the background and principles for the pilots

The architecture proposed for the pilots is described here: Pilot Design Document.

An example business case for pilots can be found here: Pilot Business Template.

About the Pilots​

The project will use pilot implementations to test and explore the thinking it develops.

We are hosting an environment that Pilots can use to participate in (see the Design Document referenced above) - however Pilots may also choose to build/use their own environment(s).

Each pilot should explore and demonstrate an approach shared with the GTR project.

  • Explore: designing, building and running the pilots will generate insights that will test and improve the recommendations and specifications.
  • Demonstrate: the pilots should show that the approach being recommended can work if adopted and deliver benefits to all participants.

The following guidelines and recommendations were presented and discussed in the meetings of 4 and 5 Sept 2025.

Core Participants​

  • Authoritative Registrar
  • Supply Chain Participant(s) - e.g.
    • Supplier and
    • Buyer
  • UN/CEFACT Global Registrar Information Directory

Candidate Actions​

Example candidate actions can be considered under two broad headings:

  • GRID Related, for example
    • Register with GRID
    • Self-maintenance of Registrar data
  • DIA related, for example
    • Issue DIA
    • Present DIA
    • Verify DIA
    • Check Registration

An example use case and set of interactions is a supply chain / trade based interaction with the issuance of a “Digital Identity Anchor” by an Authoritative Registry (AR) to a Holding Organisation (HO), and the presentation (and/or linking to) by the Holding Organisation of the DIA they have been issued to a Relying Party (RP).

Guidelines for Pilots​

Use Case​

Each pilot will be responsible for defining the use case for the parties and the interactions that they propose are part of their pilot.

Additional factors are likely to be considered for pilots, for example:

  • Digital Identity Anchor
  • Digital Conformance Credential
  • Digital Product Passport
  • Digital Facility Record
  • Other trade documentation exchanges (invoices etc.)

These will likely be chosen to reflect the particular interests of the pilot participants - the ideas they want to test and the benefits they want to explore.

Benefits​

Each pilot should consier how the pilot might emonstrate the benefit of the GRID and Digital Identity Anchor concepts. For example:

  • Authoritative Registrars who want to extend reach and visibility; and the utility and value of the data they manage; increase the competitiveness of the companies they register and enhance productivity in their jurisdiction
  • Peak Body / Industry Group / Industry Representatives who wish to reduce risk and cost in trade transactions and benefit from increased supply chain transparency
  • Software / Development / Consulting companies who want to build expertise in delivering products and services in this space

The benefits sought from the Pilot and by the participants should be declared in the pilot design.

Principles for Pilots​

The following is a list of proposed constraints/recommendations:

  • Pilots are self-sustaining. Pilots provide the resources (people/technology) they need.
  • GTR recognised Pilots need to be approved: The UN/CEFACT GTR project leads will approve pilots on the basis of the planning materials presented to them.
  • Plans are essential, shared, and evolve: The plans must be present prior to approval, but may be updated as the Pilot progresses.
  • Pilots will need to be self-run: They will determine their own way of working such that they can deliver the outcomes they seek.
  • Pilots will be supported. The UN/CEFACT project leads (and other contributors) will check on progress and provide support where possible.
  • Pilots provide feedback to the Global Trust Registry project to enable exploration and demonstration of recommendations and specifications
  • Pilot promotion: The GTR project will provide space for the Pilots to present their work in the Project environment and meetings.
  • IPR: Contributions made by pilots to the Global Trust Registry project IP will be under the general UN/CEFACT IPR rules
  • Costs are the responsibility of pilots. UN/CEFACT will provide a pretotype GRID implementation and can provide space for code/documentation and other deliverable artefacts in the UNICC GitLab environment as appropriate.
  • Pilots are not expected to be operational. To avoid the risk of confusion, it is recommended that Pilots make use of non-operational environments and dummy organisation identifiers rather than using operational systems and legal entities. HOWEVER this will be up to the pilots to decide.