05 Implementation Pilots
05 - Implementation Pilots
Document Status: Draft
Editor: John Phillips
Contributors:
1. About the project
See about the project.
Document Purpose and Scope
This document describes the implementation pilot projects of the UN/CEFACT Global Trust Registry project.
Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
2. Project Definitions
For project glossary of terms, please see the project glossary.
3. Implementation Pilots
The project anticipates running at least two pilots to test and prove the potential of the recommendations that the project will make to the UN/CEFACT Plenary and in order to provide feedback to the United Nations Transparency Protocol (UNTP) specification.
Pilot Objectives
The pilots should both explore and demonstrate the recommended approach being defined in the 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.
Pilot Design
The general pattern of Issuer | Holder | Verifier provides a basic framework for each pilot with the specific addition of the UN/CEFACT Authoritative Registry Directory.
[diagram]
Each pilot will be responsible for defining the use case the parties and the interactions that they propose are part of the pilot. A minimal 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).
Additional factors are likely to be considered for pilots, for example:
- Digital Conformance Credential
- Digital Facility Record (for land claims)
Each participant in a pilot should be seeking to explore how they might benefit from the Global Trust Registry and Digital Identity Anchor concepts:
- Authoritative Registrars who want to extend reach and visibility; and the utility and value of the data they manage
- 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.
Pilot Constraints and recommendations
-
Candidate Pilots projects must provide the project leads with initial pilot planning materials: the use case, parties, interaction sequence that they seek to demonstrate as well as the benefits that they anticipate the pilot will realise.
-
The project leads will approve pilots on the basis of the planning materials presented to them.
-
The planning artefacts must be present prior to approval to commence 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.
-
Pilot participants will be responsible for their own funding and investment in participating and developing the pilots.
-
The project leads will check on pilot progress, provide advisory support, and encourage other project contributors to support the pilots.
-
Pilots must provide feedback to the Global Trust Registry project to enable exploration and demonstration of recommendations and specifications
-
The project will provide space for the Pilots to present their work in the Project environment and meetings.
-
Contributions made by pilots to the Global Trust Registry project IP will be under the general UN/CEFACT IPR rules
-
Infrastructure costs will be the responsibility of pilot participants. UN/CEFACT can provide space for code/documentation and other deliverable artefacts in the UNICC GitLab environment as appropriate.
-
To avoid operational complication and 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.
Pilot 1 - <title>
sub-headings and text etc.
Pilot 2 - <title>
Sub-headings and text etc.
Pilot 3 - <title>
Sub-headings and text etc.