diff --git a/404.html b/404.html index 7667e08c..49af1fba 100644 --- a/404.html +++ b/404.html @@ -4,13 +4,13 @@ Page Not Found | Critical Raw Materials - +
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

- + \ No newline at end of file diff --git a/assets/js/71371426.b4877bc9.js b/assets/js/71371426.b4877bc9.js deleted file mode 100644 index d9252096..00000000 --- a/assets/js/71371426.b4877bc9.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkproject_crm_website=self.webpackChunkproject_crm_website||[]).push([[99],{5318:(e,t,a)=>{a.d(t,{Zo:()=>c,kt:()=>m});var n=a(7378);function i(e,t,a){return t in e?Object.defineProperty(e,t,{value:a,enumerable:!0,configurable:!0,writable:!0}):e[t]=a,e}function r(e,t){var a=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),a.push.apply(a,n)}return a}function l(e){for(var t=1;t=0||(i[a]=e[a]);return i}(e,t);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);for(n=0;n=0||Object.prototype.propertyIsEnumerable.call(e,a)&&(i[a]=e[a])}return i}var s=n.createContext({}),u=function(e){var t=n.useContext(s),a=t;return e&&(a="function"==typeof e?e(t):l(l({},t),e)),a},c=function(e){var t=u(e.components);return n.createElement(s.Provider,{value:t},e.children)},d={inlineCode:"code",wrapper:function(e){var t=e.children;return n.createElement(n.Fragment,{},t)}},p=n.forwardRef((function(e,t){var a=e.components,i=e.mdxType,r=e.originalType,s=e.parentName,c=o(e,["components","mdxType","originalType","parentName"]),p=u(a),m=i,h=p["".concat(s,".").concat(m)]||p[m]||d[m]||r;return a?n.createElement(h,l(l({ref:t},c),{},{components:a})):n.createElement(h,l({ref:t},c))}));function m(e,t){var a=arguments,i=t&&t.mdxType;if("string"==typeof e||i){var r=a.length,l=new Array(r);l[0]=p;var o={};for(var s in t)hasOwnProperty.call(t,s)&&(o[s]=t[s]);o.originalType=e,o.mdxType="string"==typeof e?e:i,l[1]=o;for(var u=2;u{a.d(t,{ZP:()=>l});var n=a(5773),i=(a(7378),a(5318));const r={toc:[]};function l(e){let{components:t,...a}=e;return(0,i.kt)("wrapper",(0,n.Z)({},r,a,{components:t,mdxType:"MDXLayout"}),(0,i.kt)("admonition",{type:"info"},(0,i.kt)("p",{parentName:"admonition"},"Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.")))}l.isMDXComponent=!0},7709:(e,t,a)=>{a.r(t),a.d(t,{assets:()=>u,contentTitle:()=>o,default:()=>p,frontMatter:()=>l,metadata:()=>s,toc:()=>c});var n=a(5773),i=(a(7378),a(5318)),r=a(5611);const l={title:"Interoperability Requirements"},o=void 0,s={unversionedId:"standards/Interop-requirements",id:"standards/Interop-requirements",title:"Interoperability Requirements",description:"Introduction",source:"@site/docs/standards/Interop-requirements.md",sourceDirName:"standards",slug:"/standards/Interop-requirements",permalink:"/project-crm/docs/standards/Interop-requirements",draft:!1,editUrl:"https://github.com/uncefact/project-crm/edit/main/website/docs/standards/Interop-requirements.md",tags:[],version:"current",frontMatter:{title:"Interoperability Requirements"},sidebar:"tutorialSidebar",previous:{title:"Interoperability Standards",permalink:"/project-crm/docs/standards/"},next:{title:"Implementation Guidance",permalink:"/project-crm/docs/standards/impelemntation-guidance"}},u={},c=[{value:"Introduction",id:"introduction",level:2},{value:"Document Purpose",id:"document-purpose",level:3},{value:"Audience",id:"audience",level:3},{value:"Document Context",id:"document-context",level:3},{value:"Design Principles",id:"design-principles",level:3},{value:"Design Challenges",id:"design-challenges",level:3},{value:"Scope",id:"scope",level:3},{value:"Traceability Interoperability Requirements",id:"traceability-interoperability-requirements",level:2},{value:"Traceability Data Model",id:"traceability-data-model",level:2},{value:"Transparency Data Model",id:"transparency-data-model",level:3},{value:"Identifier Schemes",id:"identifier-schemes",level:3},{value:"Verifiable Credentials",id:"verifiable-credentials",level:3},{value:"Linked Credentials",id:"linked-credentials",level:3},{value:"Trust Anchors",id:"trust-anchors",level:3},{value:"Privacy Model",id:"privacy-model",level:3},{value:"Technology Maturity",id:"technology-maturity",level:3},{value:"Physical Digital Link",id:"physical-digital-link",level:2},{value:"Provenance verification",id:"provenance-verification",level:3},{value:"Sample Value Chain",id:"sample-value-chain",level:2}],d={toc:c};function p(e){let{components:t,...a}=e;return(0,i.kt)("wrapper",(0,n.Z)({},d,a,{components:t,mdxType:"MDXLayout"}),(0,i.kt)(r.ZP,{mdxType:"Disclaimer"}),(0,i.kt)("h2",{id:"introduction"},"Introduction"),(0,i.kt)("p",null,"Some words about the need for digital traceability and the challenges about achieving it at scale. "),(0,i.kt)("h3",{id:"document-purpose"},"Document Purpose"),(0,i.kt)("p",null,"To provide the context and guide-rails for the technical deliverables such as credential schema and traceability vocabularies"),(0,i.kt)("h3",{id:"audience"},"Audience"),(0,i.kt)("p",null,"The audience for this document include"),(0,i.kt)("table",null,(0,i.kt)("thead",{parentName:"table"},(0,i.kt)("tr",{parentName:"thead"},(0,i.kt)("th",{parentName:"tr",align:null},"Role"),(0,i.kt)("th",{parentName:"tr",align:null},"Rationale"))),(0,i.kt)("tbody",{parentName:"table"},(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Mining operators"),(0,i.kt)("td",{parentName:"tr",align:null})),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Refiners & manufacturers"),(0,i.kt)("td",{parentName:"tr",align:null})),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"ESG standards & certifiers"),(0,i.kt)("td",{parentName:"tr",align:null})),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Software vendors"),(0,i.kt)("td",{parentName:"tr",align:null})),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Regulators"),(0,i.kt)("td",{parentName:"tr",align:null})))),(0,i.kt)("h3",{id:"document-context"},"Document Context"),(0,i.kt)("p",null,"TBA"),(0,i.kt)("h3",{id:"design-principles"},"Design Principles"),(0,i.kt)("p",null,"This document is guided by the following principles"),(0,i.kt)("ol",null,(0,i.kt)("li",{parentName:"ol"},"Simple and implementable always wins over expansive & complex."),(0,i.kt)("li",{parentName:"ol"},"Open and free is a fundamental requirement."),(0,i.kt)("li",{parentName:"ol"},"Collaborative development encourages buy-in"),(0,i.kt)("li",{parentName:"ol"},"Decentralised models will always be more scalable than centralised.")),(0,i.kt)("h3",{id:"design-challenges"},"Design Challenges"),(0,i.kt)("p",null,"Implementating end-to-end supply chain traceability at scale faces a number of challenges. "),(0,i.kt)("table",null,(0,i.kt)("thead",{parentName:"table"},(0,i.kt)("tr",{parentName:"thead"},(0,i.kt)("th",{parentName:"tr",align:null},"Challenge"),(0,i.kt)("th",{parentName:"tr",align:null},"Our approach"))),(0,i.kt)("tbody",{parentName:"table"},(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"A plethora of platforms exist already"),(0,i.kt)("td",{parentName:"tr",align:null},"We must focus on in interoperability between systems, not picking winners.")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Technology maturity is variable"),(0,i.kt)("td",{parentName:"tr",align:null},"We must accommodate small businesses and developing nations and allow a gradual transition from paper processes.")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Most traceability pilots have not scaled to production volumes"),(0,i.kt)("td",{parentName:"tr",align:null},"We must design simple and scalable solutions that can be implemented at scale")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Supply chain actors will not expose sensitve data"),(0,i.kt)("td",{parentName:"tr",align:null},"We must allow stakeholders to protect sensitive commercial information whilst revealing ESG info.")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"ESG claims have different levels of trust"),(0,i.kt)("td",{parentName:"tr",align:null},"We must provide sufficient evidence to trust the claims.")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Greenwashing fraud is endemic"),(0,i.kt)("td",{parentName:"tr",align:null},"We need to explicitly identify greenwashing fraud vectors and how to solve them \u2013 including product substation, mass balance, etc.")),(0,i.kt)("tr",{parentName:"tbody"},(0,i.kt)("td",{parentName:"tr",align:null},"Cost"),(0,i.kt)("td",{parentName:"tr",align:null},"The solution must be cheap enough that there remains plentiful margin incentive for producers and manufacturers to change behaviour.")))),(0,i.kt)("h3",{id:"scope"},"Scope"),(0,i.kt)("p",null,"Digital Interoperability standards for scalable traceability & transparency"),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Supply chain events"),(0,i.kt)("li",{parentName:"ul"},"entity, product & location identifiers"),(0,i.kt)("li",{parentName:"ul"},"credential schema"),(0,i.kt)("li",{parentName:"ul"},"privacy & security controls"),(0,i.kt)("li",{parentName:"ul"},"linked data vocabularies")),(0,i.kt)("h2",{id:"traceability-interoperability-requirements"},"Traceability Interoperability Requirements"),(0,i.kt)("h2",{id:"traceability-data-model"},"Traceability Data Model"),(0,i.kt)("p",null,"This section should define a specific data model of the simplest possible EPCIS event structure and vocabulary that is just sufficient for end-to-end value chain traceability. Less is more because simple low cost implementation is key. Draw upon existing UN/CEFACT vocabulary."),(0,i.kt)("h3",{id:"transparency-data-model"},"Transparency Data Model"),(0,i.kt)("p",null,"This section should define the simplest possible data model for transparency information including "),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Sensors & measurements"),(0,i.kt)("li",{parentName:"ul"},"Standards & Criteria"),(0,i.kt)("li",{parentName:"ul"},"Audits & certificates"),(0,i.kt)("li",{parentName:"ul"},"Accreditations & trust"),(0,i.kt)("li",{parentName:"ul"},"Facilities, Equipment & capacity")),(0,i.kt)("h3",{id:"identifier-schemes"},"Identifier Schemes"),(0,i.kt)("p",null,"This section should define prefered identity schemes for each type of identifier."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Legal entities (national authority schemes?)"),(0,i.kt)("li",{parentName:"ul"},"Geographic locations (plus codes?)"),(0,i.kt)("li",{parentName:"ul"},"Manufactured products (GTIN?)"),(0,i.kt)("li",{parentName:"ul"},"Bulk product (?)"),(0,i.kt)("li",{parentName:"ul"},"Manufacturing facility / equipment (Asset ID)")),(0,i.kt)("h3",{id:"verifiable-credentials"},"Verifiable Credentials"),(0,i.kt)("p",null,"This section should define VC interoperability profiles and DID methods so that the complexity of this space is simplified to a simple and implementable subset."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"VC profiles - W3C SVIP, Hyperledger Aries, "),(0,i.kt)("li",{parentName:"ul"},"DID methods for each identity type ")),(0,i.kt)("h3",{id:"linked-credentials"},"Linked Credentials"),(0,i.kt)("p",null,"This section should define a standard profile for linked credentials \u2013 ie how multiple credentials are linked together to construct a trustworthy supply chain traceability view."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Link structure (target, type, role, etc)"),(0,i.kt)("li",{parentName:"ul"},"Link integrity (eg issuer of credential is subject of linked credential etc)"),(0,i.kt)("li",{parentName:"ul"},"Verifier behaviour (how to verify a graph of linked credentials as opposed to a single credential).")),(0,i.kt)("h3",{id:"trust-anchors"},"Trust Anchors"),(0,i.kt)("p",null,"Define methods by which trust & business integrity can be attached to ESG claims"),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Trust anchors - authoritative roots of trust such as governments & national accreditation authorities. Eg Guarantee of origin certificates."),(0,i.kt)("li",{parentName:"ul"},"Peer to peer - peer to peer trust networks (is community members keeping each other honest)")),(0,i.kt)("h3",{id:"privacy-model"},"Privacy Model"),(0,i.kt)("p",null,"Define mechanisms to protect commercially sensitive information at any point in the value chain."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Document level security - encrypted storage and shared single use keys"),(0,i.kt)("li",{parentName:"ul"},"Field level security - Selective redaction methods")),(0,i.kt)("h3",{id:"technology-maturity"},"Technology Maturity"),(0,i.kt)("p",null,"Designs to support stakeholders in the value chain that have zero technology maturity."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Human Rendering templates"),(0,i.kt)("li",{parentName:"ul"},"QR links to hosted verifiers ")),(0,i.kt)("h2",{id:"physical-digital-link"},"Physical Digital Link"),(0,i.kt)("p",null,"Design solution to verifiably link the digital data to the physical shipment.."),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Finding ESG data from product ID using Digital Link resolvers"),(0,i.kt)("li",{parentName:"ul"},"Doscovering the right resolver service")),(0,i.kt)("h3",{id:"provenance-verification"},"Provenance verification"),(0,i.kt)("p",null,"List known mechanisms for provenance verifiaction"),(0,i.kt)("ul",null,(0,i.kt)("li",{parentName:"ul"},"Chemical / Istopic fingerprints")),(0,i.kt)("h2",{id:"sample-value-chain"},"Sample Value Chain"),(0,i.kt)("p",null,"Draw a simplified example for lithium/Cobalt/Copper -> EV Battery -> recycling."))}p.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/71371426.e89bee86.js b/assets/js/71371426.e89bee86.js new file mode 100644 index 00000000..0b2d72fb --- /dev/null +++ b/assets/js/71371426.e89bee86.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkproject_crm_website=self.webpackChunkproject_crm_website||[]).push([[99],{5318:(e,t,a)=>{a.d(t,{Zo:()=>d,kt:()=>m});var i=a(7378);function n(e,t,a){return t in e?Object.defineProperty(e,t,{value:a,enumerable:!0,configurable:!0,writable:!0}):e[t]=a,e}function r(e,t){var a=Object.keys(e);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);t&&(i=i.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),a.push.apply(a,i)}return a}function l(e){for(var t=1;t=0||(n[a]=e[a]);return n}(e,t);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);for(i=0;i=0||Object.prototype.propertyIsEnumerable.call(e,a)&&(n[a]=e[a])}return n}var s=i.createContext({}),c=function(e){var t=i.useContext(s),a=t;return e&&(a="function"==typeof e?e(t):l(l({},t),e)),a},d=function(e){var t=c(e.components);return i.createElement(s.Provider,{value:t},e.children)},p={inlineCode:"code",wrapper:function(e){var t=e.children;return i.createElement(i.Fragment,{},t)}},u=i.forwardRef((function(e,t){var a=e.components,n=e.mdxType,r=e.originalType,s=e.parentName,d=o(e,["components","mdxType","originalType","parentName"]),u=c(a),m=n,h=u["".concat(s,".").concat(m)]||u[m]||p[m]||r;return a?i.createElement(h,l(l({ref:t},d),{},{components:a})):i.createElement(h,l({ref:t},d))}));function m(e,t){var a=arguments,n=t&&t.mdxType;if("string"==typeof e||n){var r=a.length,l=new Array(r);l[0]=u;var o={};for(var s in t)hasOwnProperty.call(t,s)&&(o[s]=t[s]);o.originalType=e,o.mdxType="string"==typeof e?e:n,l[1]=o;for(var c=2;c{a.d(t,{ZP:()=>l});var i=a(5773),n=(a(7378),a(5318));const r={toc:[]};function l(e){let{components:t,...a}=e;return(0,n.kt)("wrapper",(0,i.Z)({},r,a,{components:t,mdxType:"MDXLayout"}),(0,n.kt)("admonition",{type:"info"},(0,n.kt)("p",{parentName:"admonition"},"Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.")))}l.isMDXComponent=!0},7709:(e,t,a)=>{a.r(t),a.d(t,{assets:()=>c,contentTitle:()=>o,default:()=>u,frontMatter:()=>l,metadata:()=>s,toc:()=>d});var i=a(5773),n=(a(7378),a(5318)),r=a(5611);const l={title:"Interoperability Requirements"},o=void 0,s={unversionedId:"standards/Interop-requirements",id:"standards/Interop-requirements",title:"Interoperability Requirements",description:"Introduction",source:"@site/docs/standards/Interop-requirements.md",sourceDirName:"standards",slug:"/standards/Interop-requirements",permalink:"/project-crm/docs/standards/Interop-requirements",draft:!1,editUrl:"https://github.com/uncefact/project-crm/edit/main/website/docs/standards/Interop-requirements.md",tags:[],version:"current",frontMatter:{title:"Interoperability Requirements"},sidebar:"tutorialSidebar",previous:{title:"Interoperability Standards",permalink:"/project-crm/docs/standards/"},next:{title:"Implementation Guidance",permalink:"/project-crm/docs/standards/impelemntation-guidance"}},c={},d=[{value:"Introduction",id:"introduction",level:2},{value:"Document Purpose",id:"document-purpose",level:3},{value:"Audience",id:"audience",level:3},{value:"Document Context",id:"document-context",level:3},{value:"Design Principles",id:"design-principles",level:3},{value:"Design Challenges",id:"design-challenges",level:3},{value:"Scope",id:"scope",level:3},{value:"Traceability Interoperability Requirements",id:"traceability-interoperability-requirements",level:2},{value:"Traceability Data Model",id:"traceability-data-model",level:2},{value:"Transparency Data Model",id:"transparency-data-model",level:3},{value:"Identifier Schemes",id:"identifier-schemes",level:3},{value:"Verifiable Credentials",id:"verifiable-credentials",level:3},{value:"Linked Credentials",id:"linked-credentials",level:3},{value:"Trust Anchors",id:"trust-anchors",level:3},{value:"Privacy Model",id:"privacy-model",level:3},{value:"Technology Maturity",id:"technology-maturity",level:3},{value:"Physical Digital Link",id:"physical-digital-link",level:2},{value:"Provenance verification",id:"provenance-verification",level:3},{value:"Sample Value Chain",id:"sample-value-chain",level:2}],p={toc:d};function u(e){let{components:t,...a}=e;return(0,n.kt)("wrapper",(0,i.Z)({},p,a,{components:t,mdxType:"MDXLayout"}),(0,n.kt)(r.ZP,{mdxType:"Disclaimer"}),(0,n.kt)("h2",{id:"introduction"},"Introduction"),(0,n.kt)("p",null,"Traceability Interoperability for the Critical Raw Materials (CRM) industry has the opportunity to help consumers, manufacturers and miners share data up, down and across the supply chain in a consistent low cost way. We also seek to provide genuine accountability and the potential for independent validation of all types of claims in the supply chain."),(0,n.kt)("p",null,"Critical Raw Materials (CRM) are paramount to the functioning of our industrial ecosystems (digital, transport, construction, renewable energy technologies, lightweight batteries). They are essential for the green energy transition.(lithium in batteries, gallium and indium in LED lamps, and rare-earth elements in magnets for digital technologies, electric vehicles and wind generators.) Such elements derived from raw minerals are \u201ccritical\u201d as they represent the most economically important source materials with high supply risk and they are concentrated in a few geographical areas. Additionally, The international CRM supply chain is growing in complexity at the same time as nation states seek to improve their border compliance for imports and facilitate access to export markets for their domestic producers. The global value chain is highly dependent on smooth cross-border supply flows (tangible, intangible and data). "),(0,n.kt)("p",null,"There is a significant commercial shift occurring in the expectations for high quality, provable credentials for ESG activities and provenance validation. The companies that are able to demonstrate provable claims about their material sourcing and ESG activities will have easier access to markets and capital. The value of traceability interoperability is to drive down the cost of sharing and demonstrating high quality credentials for provenance claims and ESG activities. By providing standards for granular, provable claims that enable independent validation and assessment, companies that are genuinely in compliance will be easily distinguished from those that cannot be validated. "),(0,n.kt)("h3",{id:"document-purpose"},"Document Purpose"),(0,n.kt)("p",null,"The purpose of this document is to define the requirements for traceability interoperability.\nThis work stream is intended to answer the \u201cHow\u201d for data exchange and the sustainability working group is answering the \u201cWhat\u201d data to exchange."),(0,n.kt)("p",null,"This document also provides the context and guide-rails for the technical deliverables for the CRM pilots such as credential schema and traceability vocabularies to drive the adoption of traceability standards that enable verifiable claims."),(0,n.kt)("h3",{id:"audience"},"Audience"),(0,n.kt)("p",null,"The primary audience for this document include the following:"),(0,n.kt)("table",null,(0,n.kt)("thead",{parentName:"table"},(0,n.kt)("tr",{parentName:"thead"},(0,n.kt)("th",{parentName:"tr",align:null},"Role"),(0,n.kt)("th",{parentName:"tr",align:null},"Rationale"))),(0,n.kt)("tbody",{parentName:"table"},(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Mining operators"),(0,n.kt)("td",{parentName:"tr",align:null},"The mining operators are the start of the value chain and for the operators that are generating the origin claims and investing in ESG activities it will be important that they can provably demonstrate their activities so that they can access markets and capital that value those investments in ESG outcomes.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Refiners & manufacturers"),(0,n.kt)("td",{parentName:"tr",align:null},"The key challenges we\u2019ll be focusing on for refiners and manufacturers will be how they demonstrate the provenance claims and ESG features of the inputs to the products that they produce and how the credentials about those inputs are 'attached' to the goods that they are producing.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"ESG standards & certifiers"),(0,n.kt)("td",{parentName:"tr",align:null},"The value of the standard and/or certifications are tied directly to the value the market places of having a trustable proof that the good or services meets the standard. A verifiable certificate provides this proof. The certification and accreditation community create an important trust anchor.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Software vendors"),(0,n.kt)("td",{parentName:"tr",align:null},"Sharing digital credentials about the material origin and ESG of data of the CRM industry is going to be powered by the digital tools that members of the supply chain use. This paper is intended to articulate how software vendors can extend their existing infrastructure in a low cost and scalable manner to support the industry.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Government organizations"),(0,n.kt)("td",{parentName:"tr",align:null},"when governments subsidise the critical minerals for strategic or national interest purposes, proof that the national interest has been met could be provided by leveraging verifiable certificate that provides the proof of the benefit.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Regulators"),(0,n.kt)("td",{parentName:"tr",align:null},"Regulators play a unique role in any value chain. They can be a trust anchor that helps their regulated community outcompete in a global marketplace. However, regulators require traceability in order to be effective. This paper will highlight principles to enable regulators to require verifiable and enforceable standards, by providing a model to corroborate and authenticate claims effectively.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"People"),(0,n.kt)("td",{parentName:"tr",align:null},"Impacts on people are generally the fundamental driver of regulatory standards. By having an avenue to weigh in on the validation process of claims, people impacted can have some leverage to ensure that regulations are followed in alignment with their original purpose. By providing evidence driven pathways for people to participate, it may be that conflicts of interest can be channeled productively into evidence gathering.")))),(0,n.kt)("h3",{id:"document-context"},"Document Context"),(0,n.kt)("p",null,"The focus of this document is traceability interoperability of the critical raw materials industry. In addition there is parallel work going in in Recommendation 49 about transparency at scale that this document will inform and we will seek guidance from. It is important that traceability interoperability works for the CRM industry in the same way as it works in adjacent and upstream industries."),(0,n.kt)("h3",{id:"design-principles"},"Design Principles"),(0,n.kt)("p",null,"This document is guided by the following principles"),(0,n.kt)("ol",null,(0,n.kt)("li",{parentName:"ol"},"Simple and implementable always wins over expansive & complex."),(0,n.kt)("li",{parentName:"ol"},"Open and free is a fundamental requirement."),(0,n.kt)("li",{parentName:"ol"},"Collaborative development encourages buy-in"),(0,n.kt)("li",{parentName:"ol"},"Decentralised models will always be more scalable than centralised."),(0,n.kt)("li",{parentName:"ol"},"Independently verifiable claims are more credible."),(0,n.kt)("li",{parentName:"ol"},"Learn and leverage from existing ecosystems, methodologies, standards and approaches.")),(0,n.kt)("h3",{id:"design-challenges"},"Design Challenges"),(0,n.kt)("p",null,"Implementing end-to-end supply chain traceability at scale faces a number of challenges. "),(0,n.kt)("table",null,(0,n.kt)("thead",{parentName:"table"},(0,n.kt)("tr",{parentName:"thead"},(0,n.kt)("th",{parentName:"tr",align:null},"Challenge"),(0,n.kt)("th",{parentName:"tr",align:null},"Our approach"))),(0,n.kt)("tbody",{parentName:"table"},(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"A plethora of platforms exist already"),(0,n.kt)("td",{parentName:"tr",align:null},"We must focus on interoperability between systems, not picking winners. We\u2019ll also provide guidance on how existing systems can extend their capability to support interoperability.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Technology maturity is variable"),(0,n.kt)("td",{parentName:"tr",align:null},"We must accommodate small businesses and developing nations and allow a gradual transition from paper processes.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Most traceability pilots have not scaled to production volumes"),(0,n.kt)("td",{parentName:"tr",align:null},"We must design simple and scalable solutions that can be implemented at scale")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Supply chain actors will not expose sensitive data"),(0,n.kt)("td",{parentName:"tr",align:null},"We must allow stakeholders to protect sensitive commercial information whilst revealing ESG info.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"ESG claims have different levels of trust"),(0,n.kt)("td",{parentName:"tr",align:null},"We must provide sufficient evidence to trust the claims.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Greenwashing fraud is endemic"),(0,n.kt)("td",{parentName:"tr",align:null},"We need to explicitly identify greenwashing fraud vectors and how to solve them \u2013 including product substation, mass balance, etc. In particular in CRM, suppliers have taken the approach of inserting a middleman and obscuring the traceability to the source. A goal of this approach must be the traceability of claims back to the point of extraction, as required by the OECD due diligence handbook.")),(0,n.kt)("tr",{parentName:"tbody"},(0,n.kt)("td",{parentName:"tr",align:null},"Cost"),(0,n.kt)("td",{parentName:"tr",align:null},"The solution must be cheap enough that there remains plentiful margin incentive for producers and manufacturers to change behaviour.")))),(0,n.kt)("h3",{id:"scope"},"Scope"),(0,n.kt)("p",null,"Digital Interoperability standards for scalable traceability & transparency"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Supply chain events"),(0,n.kt)("li",{parentName:"ul"},"Entity, product, process, time & location identifiers"),(0,n.kt)("li",{parentName:"ul"},"Credential schema"),(0,n.kt)("li",{parentName:"ul"},"Privacy & security controls"),(0,n.kt)("li",{parentName:"ul"},"Linked data vocabularies")),(0,n.kt)("h1",{id:"note-from-here-down-has-not-been-updated-as-of-oct-30th-2023--updates-are-expected-by-nov-21st-2023"},"NOTE: from here down has not been updated as of Oct 30th 2023. Updates are expected by Nov 21st 2023."),(0,n.kt)("h2",{id:"traceability-interoperability-requirements"},"Traceability Interoperability Requirements"),(0,n.kt)("h2",{id:"traceability-data-model"},"Traceability Data Model"),(0,n.kt)("p",null,"This section should define a specific data model of the simplest possible EPCIS event structure and vocabulary that is just sufficient for end-to-end value chain traceability. Less is more because simple low cost implementation is key. Draw upon existing UN/CEFACT vocabulary."),(0,n.kt)("h3",{id:"transparency-data-model"},"Transparency Data Model"),(0,n.kt)("p",null,"This section should define the simplest possible data model for transparency information including "),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Sensors & measurements"),(0,n.kt)("li",{parentName:"ul"},"Standards & Criteria"),(0,n.kt)("li",{parentName:"ul"},"Audits & certificates"),(0,n.kt)("li",{parentName:"ul"},"Accreditations & trust"),(0,n.kt)("li",{parentName:"ul"},"Facilities, Equipment & capacity")),(0,n.kt)("h3",{id:"identifier-schemes"},"Identifier Schemes"),(0,n.kt)("p",null,"This section should define prefered identity schemes for each type of identifier."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Legal entities (national authority schemes?)"),(0,n.kt)("li",{parentName:"ul"},"Geographic locations (plus codes?)"),(0,n.kt)("li",{parentName:"ul"},"Manufactured products (GTIN?)"),(0,n.kt)("li",{parentName:"ul"},"Bulk product (?)"),(0,n.kt)("li",{parentName:"ul"},"Manufacturing facility / equipment (Asset ID)")),(0,n.kt)("h3",{id:"verifiable-credentials"},"Verifiable Credentials"),(0,n.kt)("p",null,"This section should define VC interoperability profiles and DID methods so that the complexity of this space is simplified to a simple and implementable subset."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"VC profiles - W3C SVIP, Hyperledger Aries, "),(0,n.kt)("li",{parentName:"ul"},"DID methods for each identity type ")),(0,n.kt)("h3",{id:"linked-credentials"},"Linked Credentials"),(0,n.kt)("p",null,"This section should define a standard profile for linked credentials \u2013 ie how multiple credentials are linked together to construct a trustworthy supply chain traceability view."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Link structure (target, type, role, etc)"),(0,n.kt)("li",{parentName:"ul"},"Link integrity (eg issuer of credential is subject of linked credential etc)"),(0,n.kt)("li",{parentName:"ul"},"Verifier behaviour (how to verify a graph of linked credentials as opposed to a single credential).")),(0,n.kt)("h3",{id:"trust-anchors"},"Trust Anchors"),(0,n.kt)("p",null,"Define methods by which trust & business integrity can be attached to ESG claims"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Trust anchors - authoritative roots of trust such as governments & national accreditation authorities. Eg Guarantee of origin certificates."),(0,n.kt)("li",{parentName:"ul"},"Peer to peer - peer to peer trust networks (is community members keeping each other honest)")),(0,n.kt)("h3",{id:"privacy-model"},"Privacy Model"),(0,n.kt)("p",null,"Define mechanisms to protect commercially sensitive information at any point in the value chain."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Document level security - encrypted storage and shared single use keys"),(0,n.kt)("li",{parentName:"ul"},"Field level security - Selective redaction methods")),(0,n.kt)("h3",{id:"technology-maturity"},"Technology Maturity"),(0,n.kt)("p",null,"Designs to support stakeholders in the value chain that have zero technology maturity."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Human Rendering templates"),(0,n.kt)("li",{parentName:"ul"},"QR links to hosted verifiers ")),(0,n.kt)("h2",{id:"physical-digital-link"},"Physical Digital Link"),(0,n.kt)("p",null,"Design solution to verifiably link the digital data to the physical shipment.."),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Finding ESG data from product ID using Digital Link resolvers"),(0,n.kt)("li",{parentName:"ul"},"Doscovering the right resolver service")),(0,n.kt)("h3",{id:"provenance-verification"},"Provenance verification"),(0,n.kt)("p",null,"List known mechanisms for provenance verifiaction"),(0,n.kt)("ul",null,(0,n.kt)("li",{parentName:"ul"},"Chemical / Istopic fingerprints")),(0,n.kt)("h2",{id:"sample-value-chain"},"Sample Value Chain"),(0,n.kt)("p",null,"Draw a simplified example for lithium/Cobalt/Copper -> EV Battery -> recycling."))}u.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.b7d42363.js b/assets/js/runtime~main.c8f1616c.js similarity index 98% rename from assets/js/runtime~main.b7d42363.js rename to assets/js/runtime~main.c8f1616c.js index 6e112276..4d52f26d 100644 --- a/assets/js/runtime~main.b7d42363.js +++ b/assets/js/runtime~main.c8f1616c.js @@ -1 +1 @@ -(()=>{"use strict";var e,t,r,f,a,o={},n={};function b(e){var t=n[e];if(void 0!==t)return t.exports;var r=n[e]={id:e,loaded:!1,exports:{}};return o[e].call(r.exports,r,r.exports,b),r.loaded=!0,r.exports}b.m=o,b.c=n,e=[],b.O=(t,r,f,a)=>{if(!r){var o=1/0;for(i=0;i=a)&&Object.keys(b.O).every((e=>b.O[e](r[d])))?r.splice(d--,1):(n=!1,a0&&e[i-1][2]>a;i--)e[i]=e[i-1];e[i]=[r,f,a]},b.n=e=>{var t=e&&e.__esModule?()=>e.default:()=>e;return b.d(t,{a:t}),t},r=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,b.t=function(e,f){if(1&f&&(e=this(e)),8&f)return e;if("object"==typeof e&&e){if(4&f&&e.__esModule)return e;if(16&f&&"function"==typeof e.then)return e}var a=Object.create(null);b.r(a);var o={};t=t||[null,r({}),r([]),r(r)];for(var n=2&f&&e;"object"==typeof n&&!~t.indexOf(n);n=r(n))Object.getOwnPropertyNames(n).forEach((t=>o[t]=()=>e[t]));return o.default=()=>e,b.d(a,o),a},b.d=(e,t)=>{for(var r in t)b.o(t,r)&&!b.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},b.f={},b.e=e=>Promise.all(Object.keys(b.f).reduce(((t,r)=>(b.f[r](e,t),t)),[])),b.u=e=>"assets/js/"+({37:"fbc628b1",50:"f0d09e90",52:"8e33b65d",53:"935f2afb",65:"f046f547",85:"1f391b9e",92:"7685e8c6",99:"71371426",195:"c4f5d8e4",237:"935aa1b1",279:"fe5cdad1",293:"1b4031b8",331:"4152776b",389:"79f08f9d",455:"51611adf",489:"9de25e1e",504:"88318ebb",514:"1be78505",543:"4aa02d1e",610:"7f4f1c42",630:"0f19e030",719:"445e7840",720:"b0ef66bf",767:"d8a39436",771:"9b74b6c5",802:"9cefeb0a",878:"88933e3e",918:"17896441"}[e]||e)+"."+{37:"d9d5021c",50:"27ad2c82",52:"b7f9bdbe",53:"6d562c24",65:"0569abbc",74:"ea95ddf4",85:"3b12c272",92:"69aef04b",99:"b4877bc9",195:"00d7a153",237:"f47bdb34",279:"166930fc",293:"2be5f9e1",331:"74c8dfa0",389:"253eaf04",455:"abfa2535",489:"02891445",504:"c8dbe8af",514:"b0a86bf4",543:"e09bf20f",610:"d6b31119",630:"eb41c3c8",719:"2b26b468",720:"47174f27",767:"014b4379",771:"f02d6f6c",802:"d3ec36a5",878:"3c934483",893:"a8b7aeb3",918:"d6927e3f"}[e]+".js",b.miniCssF=e=>{},b.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),b.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),f={},a="project-crm-website:",b.l=(e,t,r,o)=>{if(f[e])f[e].push(t);else{var n,d;if(void 0!==r)for(var c=document.getElementsByTagName("script"),i=0;i{n.onerror=n.onload=null,clearTimeout(s);var a=f[e];if(delete f[e],n.parentNode&&n.parentNode.removeChild(n),a&&a.forEach((e=>e(r))),t)return t(r)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:n}),12e4);n.onerror=l.bind(null,n.onerror),n.onload=l.bind(null,n.onload),d&&document.head.appendChild(n)}},b.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},b.p="/project-crm/",b.gca=function(e){return e={17896441:"918",71371426:"99",fbc628b1:"37",f0d09e90:"50","8e33b65d":"52","935f2afb":"53",f046f547:"65","1f391b9e":"85","7685e8c6":"92",c4f5d8e4:"195","935aa1b1":"237",fe5cdad1:"279","1b4031b8":"293","4152776b":"331","79f08f9d":"389","51611adf":"455","9de25e1e":"489","88318ebb":"504","1be78505":"514","4aa02d1e":"543","7f4f1c42":"610","0f19e030":"630","445e7840":"719",b0ef66bf:"720",d8a39436:"767","9b74b6c5":"771","9cefeb0a":"802","88933e3e":"878"}[e]||e,b.p+b.u(e)},(()=>{var e={303:0,532:0};b.f.j=(t,r)=>{var f=b.o(e,t)?e[t]:void 0;if(0!==f)if(f)r.push(f[2]);else if(/^(303|532)$/.test(t))e[t]=0;else{var a=new Promise(((r,a)=>f=e[t]=[r,a]));r.push(f[2]=a);var o=b.p+b.u(t),n=new Error;b.l(o,(r=>{if(b.o(e,t)&&(0!==(f=e[t])&&(e[t]=void 0),f)){var a=r&&("load"===r.type?"missing":r.type),o=r&&r.target&&r.target.src;n.message="Loading chunk "+t+" failed.\n("+a+": "+o+")",n.name="ChunkLoadError",n.type=a,n.request=o,f[1](n)}}),"chunk-"+t,t)}},b.O.j=t=>0===e[t];var t=(t,r)=>{var f,a,o=r[0],n=r[1],d=r[2],c=0;if(o.some((t=>0!==e[t]))){for(f in n)b.o(n,f)&&(b.m[f]=n[f]);if(d)var i=d(b)}for(t&&t(r);c{"use strict";var e,t,r,f,a,o={},n={};function b(e){var t=n[e];if(void 0!==t)return t.exports;var r=n[e]={id:e,loaded:!1,exports:{}};return o[e].call(r.exports,r,r.exports,b),r.loaded=!0,r.exports}b.m=o,b.c=n,e=[],b.O=(t,r,f,a)=>{if(!r){var o=1/0;for(i=0;i=a)&&Object.keys(b.O).every((e=>b.O[e](r[d])))?r.splice(d--,1):(n=!1,a0&&e[i-1][2]>a;i--)e[i]=e[i-1];e[i]=[r,f,a]},b.n=e=>{var t=e&&e.__esModule?()=>e.default:()=>e;return b.d(t,{a:t}),t},r=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,b.t=function(e,f){if(1&f&&(e=this(e)),8&f)return e;if("object"==typeof e&&e){if(4&f&&e.__esModule)return e;if(16&f&&"function"==typeof e.then)return e}var a=Object.create(null);b.r(a);var o={};t=t||[null,r({}),r([]),r(r)];for(var n=2&f&&e;"object"==typeof n&&!~t.indexOf(n);n=r(n))Object.getOwnPropertyNames(n).forEach((t=>o[t]=()=>e[t]));return o.default=()=>e,b.d(a,o),a},b.d=(e,t)=>{for(var r in t)b.o(t,r)&&!b.o(e,r)&&Object.defineProperty(e,r,{enumerable:!0,get:t[r]})},b.f={},b.e=e=>Promise.all(Object.keys(b.f).reduce(((t,r)=>(b.f[r](e,t),t)),[])),b.u=e=>"assets/js/"+({37:"fbc628b1",50:"f0d09e90",52:"8e33b65d",53:"935f2afb",65:"f046f547",85:"1f391b9e",92:"7685e8c6",99:"71371426",195:"c4f5d8e4",237:"935aa1b1",279:"fe5cdad1",293:"1b4031b8",331:"4152776b",389:"79f08f9d",455:"51611adf",489:"9de25e1e",504:"88318ebb",514:"1be78505",543:"4aa02d1e",610:"7f4f1c42",630:"0f19e030",719:"445e7840",720:"b0ef66bf",767:"d8a39436",771:"9b74b6c5",802:"9cefeb0a",878:"88933e3e",918:"17896441"}[e]||e)+"."+{37:"d9d5021c",50:"27ad2c82",52:"b7f9bdbe",53:"6d562c24",65:"0569abbc",74:"ea95ddf4",85:"3b12c272",92:"69aef04b",99:"e89bee86",195:"00d7a153",237:"f47bdb34",279:"166930fc",293:"2be5f9e1",331:"74c8dfa0",389:"253eaf04",455:"abfa2535",489:"02891445",504:"c8dbe8af",514:"b0a86bf4",543:"e09bf20f",610:"d6b31119",630:"eb41c3c8",719:"2b26b468",720:"47174f27",767:"014b4379",771:"f02d6f6c",802:"d3ec36a5",878:"3c934483",893:"a8b7aeb3",918:"d6927e3f"}[e]+".js",b.miniCssF=e=>{},b.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),b.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),f={},a="project-crm-website:",b.l=(e,t,r,o)=>{if(f[e])f[e].push(t);else{var n,d;if(void 0!==r)for(var c=document.getElementsByTagName("script"),i=0;i{n.onerror=n.onload=null,clearTimeout(s);var a=f[e];if(delete f[e],n.parentNode&&n.parentNode.removeChild(n),a&&a.forEach((e=>e(r))),t)return t(r)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:n}),12e4);n.onerror=l.bind(null,n.onerror),n.onload=l.bind(null,n.onload),d&&document.head.appendChild(n)}},b.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},b.p="/project-crm/",b.gca=function(e){return e={17896441:"918",71371426:"99",fbc628b1:"37",f0d09e90:"50","8e33b65d":"52","935f2afb":"53",f046f547:"65","1f391b9e":"85","7685e8c6":"92",c4f5d8e4:"195","935aa1b1":"237",fe5cdad1:"279","1b4031b8":"293","4152776b":"331","79f08f9d":"389","51611adf":"455","9de25e1e":"489","88318ebb":"504","1be78505":"514","4aa02d1e":"543","7f4f1c42":"610","0f19e030":"630","445e7840":"719",b0ef66bf:"720",d8a39436:"767","9b74b6c5":"771","9cefeb0a":"802","88933e3e":"878"}[e]||e,b.p+b.u(e)},(()=>{var e={303:0,532:0};b.f.j=(t,r)=>{var f=b.o(e,t)?e[t]:void 0;if(0!==f)if(f)r.push(f[2]);else if(/^(303|532)$/.test(t))e[t]=0;else{var a=new Promise(((r,a)=>f=e[t]=[r,a]));r.push(f[2]=a);var o=b.p+b.u(t),n=new Error;b.l(o,(r=>{if(b.o(e,t)&&(0!==(f=e[t])&&(e[t]=void 0),f)){var a=r&&("load"===r.type?"missing":r.type),o=r&&r.target&&r.target.src;n.message="Loading chunk "+t+" failed.\n("+a+": "+o+")",n.name="ChunkLoadError",n.type=a,n.request=o,f[1](n)}}),"chunk-"+t,t)}},b.O.j=t=>0===e[t];var t=(t,r)=>{var f,a,o=r[0],n=r[1],d=r[2],c=0;if(o.some((t=>0!==e[t]))){for(f in n)b.o(n,f)&&(b.m[f]=n[f]);if(d)var i=d(b)}for(t&&t(r);c About this project | Critical Raw Materials - +

About this project

Critical raw materials sustainability & resilience​

In line with the UN sustainability goals and building on the success of the UNECE Textile & Leather traceability project, this project seeks to develop a traceability and sustainability framework for critical raw materials (CRM). This project supports the UN focus on extractive industries and builds on the UN/CEFACT role & capabilities to deliver digital standards for sustainable supply chains.

The purpose of this project is to combat greenwashing and uplift verifiable critical raw materials supply chain sustainability and resilience.

  • Sustainable supply chains are designed to minimize environmental impacts and maximise human welfare.
  • Resilient supply chains are designed to avoid risky dependencies and can withstand disruptions.

Both goals are met through digitising traceability and transparency at scale. In order to scale from pilots to global scale production volumes, this project focuses on two key challenges

  • Interoperability: There are different types of supply chain traceability platforms on the market. Since they will not lead the world’s supply chains, end-to-end traceability will depend on standards-based interoperability between platforms. This project will define interoperability standards and implementation test services in which supply chain actors can pick any compliant platform.
  • Core Vocabulary: There are already hundreds of ESG standards or related criteria as well as several emerging regulatory criteria specific to geographic or industrial sectors. This complexity imposes challenges for supply chain actors who must understand how their domestic sustainability measures map to the standards or regulatory criteria of their export markets. This project will focus on the mapping of current ESG standards by developing a core vocabulary of criteria and a legal framework for mutual recognition.

Greenwashing​

Greenwashing is a term used to describe a false, misleading, or untrue action or set of claims made by an organization about the positive impact that a company, product or service has on the environment or on social welfare.

The evidence from multiple research activities is that greenwashing is already endemic with around 60% of claims being proven to be false or misleading. But there is room for optimism because around 70% of consumers expect higher integrity behaviour and are willing to pay for it. There are two plausible pathways ahead of us.

race to the top or bottom

To win the race to the top, fake claims need to be hard to make. The best way to achieve that is to make supply chains traceable and transparent so that unsustainable practices have nowhere to hide. But, to have any impact, the traceability and transparency measures must be implemented at scale. The world's supply chains must move beyond low-volume traceability pilots and "walled garden" proprietary solutions to the point where verifiable traceability and transparency information is available to motivate consumers for the majority of products on the market.

Therefore, scalability and associated evidence of high-volume production implementation is this project's key measure of success. We will be able to claim a moderate level of success for the pilot implementation phase if we have evidence that:

  • at least 50 different CRM supply chain actors
  • using at least 5 different software platforms
  • across at least 5 different value chains
  • spanning at least 5 different countries
  • can reveal transparent supply chain evidence for at least 10,000 consignments.

To win the race to the top, fake claims need to be hard to make. The best way to achieve that is to make supply chains traceable and transparent so that unsustainable practices have nowhere to hide. But, to have any impact, traceability and transparency measures must be implemented at scale. The world’s supply chains must move beyond low-volume traceability pilots and "walled garden" proprietary solutions to the point where verifiable traceability and transparency information is available to motivate consumers for most products on the market.

This is still a tiny fraction of actual global trade volumes but is probably sufficient to prove that the framework is scalable.

Participation​

This project will be of interest to primary producers, manufacturers, regulators, ESG standards authorities, certifiers, and ESG/traceability software solution vendors.

Under the UN/CEFACT Open Development Process (ODP), participation in this project is open to all. There are three types of participation:

  • Observers: Anyone who is interested in following the activities and outcomes from this project but will not be actively contributing to the standards development work nor participating in pilot implementations. Observers may join the conversation on our Slack channel and/or subscribe to our monthly project newsletter.
  • Contributors Anyone who is able to provide the skills and commitment to contribute to standards development. Participants in this category should either have deep business domain knowledge in CRM supply chain sustainability or technical skills in decentralized architectures and data modeling. As a contributor, you must conform to UN/CEFACT IPR policy and must join UN/CEFACT as a registered expert. Note that this will require the approval of your country's head of delegation.
  • Implementers: Any CRM supply chain actor (e.g. producer, manufacturer, certifier, software vendor) that wishes to participate in early pilots and/or certify their software against the standards defined by this project.

Please email the project lead if you wish to participate as a contributor or implementer.

Reference material​

Frequently Asked Questions

1. What are critical raw materials (CRMs)?​

Critical minerals are metals and non-metals, such as cobalt or lithium, that are considered essential to the economy and whose supply may be at risk due to geological scarcity, geopolitical issues, trade policy or other factors.

2. Why do CRMs require high levels of traceability?​

Due to their scarcity and concentration in select geographic regions, many countries rely on the import of CRMs, creating a high supply risk. Critical minerals receive increased pressure for traceability in accordance with international climate regulation, and digital technology has been identified as a valuable tool to support these initiatives.  

3. What is the UN/CEFACT Critical Raw Materials Traceability and Sustainability Project?​

Critical raw material (CRM) producers provide essential materials like lithium, cobalt, copper, and graphite to countries across the world. CRM supply chains are often long and complex, involving multiple organizations and crossing several international borders as materials move from raw material extraction to finished products.

Globally, sustainability data is held on various platforms using differing standards. CRM producers are increasingly being asked to meet a range of evolving domestic and international requirements to satisfy regulatory and consumer demand. There are many supply chain traceability solutions on the market, but most do not allow data to be shared between them. CRM producers need an efficient and trustworthy way to prove their sustainability performance along international supply chains.

The UN/CEFACT Critical Raw Materials Traceability and Sustainability Project (CRM Project) is connecting experts from across the world to research current international sustainability standards and reporting platforms. The project will use this research to identify ways to improve compatibility between current sustainability standards and digital tools and create a framework for international data exchange that increases trust and traceability.

With simple and secure methods to prove their sustainability performance, actors along CRM supply chains are better positioned to compete in global markets that prioritize sustainable goods, encouraging a wider adherence to responsible mining practices.

4. What is the CRM Project trying to achieve?​

The CRM project seeks to make CRM supply chains more sustainable and resilient by improving transparency and traceability.

  • Sustainable supply chains minimize environmental impacts and maximise human welfare.
  • Resilient supply chains avoid risky dependencies and can withstand disruptions.

The CRM Project aims to create standards for:

  1. Compatibility between digital tools and reporting platforms;
  2. Identifying areas of consensus within existing sustainability certifications.

These standards will enable data to be exchanged internationally, making it easier to prove where and how critical raw materials are extracted and used.

5. Who is hosting the CRM Project?​

The CRM project is hosted by the UN Centre for Trade Facilitation and Electronic-Business (UN/CEFACT).

Building on the success of the Textile and Leather Traceability project, the CRM project unites organizations from around the world, and all organizations are welcome to participate.

6. What is the timeline for the CRM Project?​

The CRM project has been divided into several phases of work:

TimingProject Stage
May 2023Project Inception
June 2023Call for Participation
July 2023Requirements Gathering
August 2023 - August 2024Development of Draft Deliverables
September 2024 - March 2025Implementation Testing
April-May 2025Public Draft Review
June 2025Project Exit

7. How is the CRM Project aligning with existing initiatives?​

The CRM project embraces all environmental, social, and governance (ESG) platforms, standards, and regulations. Our environmental scan illustrates the broad range of platforms, standards, and regulations that inform the project work.

The CRM project will not create a new traceability platform, nor will it define new sustainability standards. Instead, this project is focused on increasing the compatibility and identifying points of consensus between existing tools and standards.

We welcome participation from CRM supply chain participants, technology providers, standards authorities, and regulators to ensure that their work is considered as the project examines tools and regulations across jurisdictional boundaries.

The CRM project will undertake analysis to understand legal and governance considerations related to supply chains. This research will include considerations of how audit and verification processes are connected and recognized across multiple jurisdictions.

9. What is the scope of work for the CRM project?​

The CRM project covers a broad spectrum of environmental, social, and governance (ESG) concerns as they relate to both regulatory purposes and consumer demand.

Existing initiatives, such as the Global Battery Alliance, have identified a range of issues that are valuable to regulators and consumers. The CRM project will build on the work of existing initiatives to focus on areas of work that are of the highest priority for the global community.

The CRM project will not recreate or reinvent ESG standards or traceability solutions. Rather, this work will focus on mapping between existing standards and providing a framework for determining points of convergence. This includes primary production to finished product, encompassing all stages of supply chain exchange.

10. Which digital platform will the CRM project use?​

The CRM project will not identify a single platform or technical solution. There are thousands of platforms for the exchange of sustainability data worldwide, and the challenge being explored cannot be solved with a single tool. Our focus is on the exchange of trusted data between many users across various platforms.

Technology vendors are welcome to participate in the project through voluntary contributions to standard development and implementation testing. This offers the opportunity to be listed as a compliant vendor by UN/CEFACT.

11. Why is the CRM Project focused on decentralization?​

In the journey from extraction to final product, information about a critical mineral shipment crosses multiple countries, sectors, and technology platforms.

Successful global scale data exchange is reliant on:

  • a range of interoperable tools, and,
  • consensus on data standards and policies.

While the CRM project aims to identify tools and standards for critical raw material supply chains, there are examples of this model at work for other purposes worldwide today, demonstrating the viability of this model.

For example, a traveler with a Canadian passport can enter Australia without the need for an Australian passport. There are existing policies in place that enable the Canadian passport to be recognized by Australian border patrol. There is no need for a single, central database of global passports since the standards between Canada and Australia are mutually recognizable.

12. How can I participate in the CRM Project?​

There are three ways that organizations across the world can get involved:  

  • Contributors participate in meetings, draft key deliverables, and support policy recommendations.  
  • Observers join meetings, receive emails, and participate in the Slack chat to stay informed on project progress.  
  • Implementers will test and offer feedback on project standards and deliverables after drafts are completed.  

13. What is the time commitment for participation? ​

Participation in the CRM project is voluntary, meaning that we welcome as much or as little time as participants are able to commit. The average expected time commitment depends on the level of participation:

  • Contributors – 4-8 hours per week.
  • Observers – As needed.
  • Implementers – 4-8 hours per week, during the implementation phase.

14. How will my contributions be used?​

Contributors to the CRM Project will register as UN Experts. We are happy to assist you with this process if you are not already registered. All contributions made to this project are the intellectual property of the UN.

Ideas, deliverables, or language developed as part of this project cannot be commercialized or patented.

15. What value will I receive from participating in the CRM Project?​

This project offers value to many different sectors, but will be of particular interest to:

  • Primary Producers & Manufacturers: Digital technology has the potential to reduce the administrative burden of sustainability reporting, streamline business processes, and lower the cost of ESG compliance. Using interoperable technology, CRM producers can share information about their sustainable practices in seconds. By proving their ESG performance, CRM producers are better positioned to compete in global markets that prioritize sustainable goods.
  • Certifiers, Auditors, and Standards Setters: As more companies are incentivized to comply with ESG regulations, the demand for sustainability audits will increase. Current certifications, standards, and audit reports will become more valuable as they become globally recognized.
  • Software Providers: Technology platforms that are compatible with other platforms offer higher value to customers who need to exchange credentials internationally.
- + \ No newline at end of file diff --git a/docs/deliverables/CRMProjectFAQ/index.html b/docs/deliverables/CRMProjectFAQ/index.html index c032dab5..6910cd72 100644 --- a/docs/deliverables/CRMProjectFAQ/index.html +++ b/docs/deliverables/CRMProjectFAQ/index.html @@ -4,13 +4,13 @@ Frequently Asked Questions | Critical Raw Materials - +

Frequently Asked Questions

1. What are critical raw materials (CRMs)?​

Critical minerals are metals and non-metals, such as cobalt or lithium, that are considered essential to the economy and whose supply may be at risk due to geological scarcity, geopolitical issues, trade policy or other factors.

2. Why do CRMs require high levels of traceability?​

Due to their scarcity and concentration in select geographic regions, many countries rely on the import of CRMs, creating a high supply risk. Critical minerals receive increased pressure for traceability in accordance with international climate regulation, and digital technology has been identified as a valuable tool to support these initiatives.  

3. What is the UN/CEFACT Critical Raw Materials Traceability and Sustainability Project?​

Critical raw material (CRM) producers provide essential materials like lithium, cobalt, copper and graphite to countries across the world. CRM supply chains are often long and complex, involving multiple organizations and crossing several international borders as materials move from raw material extraction to finished product.

Globally, sustainability data is held on various platforms using differing standards. CRM producers are increasingly being asked to meet a range of evolving domestic and international requirements to satisfy regulatory and consumer demand. There are many supply chain traceability solutions on the market, but most do not allow data to be shared between them. CRM producers need an efficient and trustworthy way to prove their sustainability performance along international supply chains.

The UN/CEFACT Critical Raw Materials Traceability and Sustainability Project (CRM Project) is connecting experts from across the world to research current international sustainability standards and reporting platforms. The project will use this research to identify ways to improve compatibility between current sustainability standards and digital tools and create a framework for international data exchange that increases trust and traceability.

With simple and secure methods to prove their sustainability performance, actors along CRM supply chains are better positioned to compete in global markets that prioritize sustainable goods, encouraging a wider adherence to responsible mining practices.

4. What is the CRM Project trying to achieve?​

The CRM project is seeking to make CRM supply chains more sustainable and resilient by improving transparency and traceability.

  • Sustainable supply chains minimize environmental impacts and maximise human welfare.
  • Resilient supply chains avoid risky dependencies and can withstand disruptions.

The CRM Project aims to create standards for:

  1. Compatibility between digital tools and reporting platforms;
  2. Identifying areas of consensus within existing sustainability certifications.

These standards will enable data to be exchanged internationally, making it easier to prove where and how critical raw materials are extracted and used.

5. Who is hosting the CRM Project?​

The CRM project is hosted by the UN Centre for Trade Facilitation and Electronic-Business (UN/CEFACT).

Building on the success of the Textile and Leather Traceability project, the CRM project unites organizations from around the world, and all organizations are welcome to participate.

6. What is the timeline for the CRM Project?​

The CRM project has been divided into several phases of work:

TimingProject Stage
May 2023Project Inception
June 2023Call for Participation
July 2023Requirements Gathering
August 2023 - August 2024Development of Draft Deliverables
September 2024 - March 2025Implementation Testing
April-May 2025Public Draft Review
June 2025Project Exit

7. How is the CRM Project aligning with existing initiatives?​

The CRM project embraces all environmental, social, and governance (ESG) platforms, standards, and regulations. Our environmental scan illustrates the broad range of platforms, standards, and regulation that inform the project work.

The CRM project will not create a new traceability platform, nor will it define new sustainability standards. Instead, this project is focused on increasing the compatibility and identifying points of consensus between existing tools and standards.

We welcome participation from CRM supply chain participants, technology providers, standards authorities, and regulators to ensure that their work is considered as the project examines tools and regulation across jurisdictional boundaries.

The CRM project will undertake analysis to understand legal and governance considerations related to supply chains. This research will include considerations of how audit and verification processes are connected and recognized across multiple jurisdictions.

9. What is the scope of work for the CRM project?​

The CRM project covers a broad spectrum of environmental, social, and governance (ESG) concerns as they relate to both regulatory purposes and consumer demand.

Existing initiatives, such as the Global Battery Alliance, have identified a range of issues that are valuable to regulators and consumers. The CRM project will build on the work of existing initiatives to focus on areas of work that are of highest priority for the global community.

The CRM project will not recreate or reinvent ESG standards or traceability solutions. Rather, this work will focus on mapping between existing standards and providing a framework for determining points of convergence. This includes primary production to finished product, encompassing all stages of supply chain exchange.

10. Which digital platform will the CRM project use?​

The CRM project will not identify a single platform or technical solution. There are thousands of platforms for the exchange of sustainability data worldwide, and the challenge being explored cannot be solved with a single tool. Our focus is on the exchange of trusted data between many users across various platforms.

Technology vendors are welcome to participate in the project through voluntary contribution to standard development and implementation testing. This offers the opportunity to be listed as a compliant vendor by UN/CEFACT.

11. Why is the CRM Project focused on decentralization?​

In the journey from extraction to final product, information about a critical mineral shipment crosses multiple countries, sectors, and technology platforms.

Successful global scale data exchange is reliant on:

  • a range of interoperable tools, and,
  • consensus on data standards and policies.

While the CRM project is aiming to identify tools and standards for critical raw material supply chains, there are examples of this model at work for other purposes worldwide today, demonstrating the viability of this model.

For example, a traveller with a Canadian passport can enter Australia without the need for an Australian passport. There are existing policies in place that enable the Canadian passport to be recognized by Australian border patrol. There is no need for a single, central database of global passports, since the standards between Canada and Australia are mutually recognizable.

12. How can I participate in the CRM Project?​

There are three ways that organizations across the world can get involved:  

  • Contributors participate in meetings, draft key deliverables, and support policy recommendations.  
  • Observers join meetings, receive emails, and participate in the Slack chat to stay informed on project progress.  
  • Implementers will test and offer feedback on project standards and deliverables after drafts are completed.  

13. What is the time commitment for participation? ​

Participation in the CRM project is voluntary, meaning that we welcome as much or as little time as participants are able to commit. The average expected time commitment depends on the level of participation:

  • Contributors – 4-8 hours per week.
  • Observers – As needed.
  • Implementers – 4-8 hours per week, during implementation phase.

14. How will my contributions be used?​

Contributors to the CRM Project will register as UN Experts. We are happy to assist you with this process if you are not already registered. All contributions made to this project are the intellectual property of the UN.

Ideas, deliverables, or language developed as part of this project cannot be commercialised or patented.

15. What value will I receive from participating in the CRM Project?​

This project offers value to many different sectors, but will be of particular interest to:

  • Primary Producers & Manufacturers: Digital technology has the potential to reduce the administrative burden of sustainability reporting, streamline business processes, and lower the cost of ESG compliance. Using interoperable technology, CRM producers can share information about their sustainable practices in seconds. By proving their ESG performance, CRM producers are better positioned to compete in global markets that prioritize sustainable goods.
  • Certifiers, Auditors, and Standards Setters: As more companies are incentivized to comply with ESG regulation, the demand for sustainability audits will increase. Current certifications, standards, and audit reports will become more valuable as they become globally recognized.
  • Software Providers: Technology platforms that are compatible with other platforms offer higher value to customers who need to exchange credentials internationally.
- + \ No newline at end of file diff --git a/docs/deliverables/ToR/index.html b/docs/deliverables/ToR/index.html index 407a625d..d7f28952 100644 --- a/docs/deliverables/ToR/index.html +++ b/docs/deliverables/ToR/index.html @@ -4,14 +4,14 @@ Terms of Reference | Critical Raw Materials - +

Terms of Reference

Project Purpose​

The purpose of this project is to create for the trusted exchange of supply chain sustainability information between traceability platforms in a scalable, high integrity, low cost, and privacy-preserving manner.

Project Objectives​

  • We aim to facilitate and prove scalable technical interoperability (data portability). We are not creating another traceability platform nor are we planning to pick any winners.
  • We aim to scale mutual recognition of sustainability standards and jurisdictional regulations through equivalency mapping and creating (or building on existing) frameworks for determining points of convergence. We are not defining new sustainability standards.

Principles​

  • UN/CEFACT Open Development Process is consensus driven, collaborative, open and transparent.
  • Aligned to UN SDGs (United Nations Sustainable Development Goals).
  • The project will define and deliver practical, useful ways to add value. We will build real useable tools that facilitate global implementations.
  • The project will build upon related work already completed and underway by UN/CEFACT and other organizations and initiatives.

Governance​

  • Project Lead (Nancy Norris): The Project Lead will coordinate the planning, implementation and monitoring of activities. The Project Lead will facilitate the implementation of the project in all its stages and provide leadership in alignment with the UN/CEFACT’s goals throughout the context of the project.
  • Lead Editor (Steven Capell): The Lead Editor will collate (and edit as necessary) contributions from team members / sub-editors. If there are conflicting opinions on a topic from the team, the lead editor will seek consensus wherever possible and make decisions as a design authority between possible options in accordance with the project goals & principles.
  • Sub Working Group Leads: Each work stream will have an associated sub working group with a lead. The Working group lead is responsible for organizing meetings, consolidating the working groups’ contribution to the draft deliverables, and reporting on progress to the Contributors Working Group on a bi-weekly basis.
  • UN/CEFACT Bureau & Secretariat: The UN/CEFACT Bureau collectively represents the community of, the members of and contributors to UN/CEFACT. It works on the development of the Centre and its recognition at the international level as the reference entity for global Trade Facilitation and Electronic Business. The Secretariat supports the UN/CEFACT program of work.
  • Heads of Delegation: Heads of Delegation represent their member States on a standing basis, as well as to provide a mechanism to ensure effective public-private partnership in this UNECE programme and its monitoring by member States.

Participant types​

  • Observer: Participants who are not active contributors but nevertheless want to maintain a watching brief on the UN/CEFACT project.
  • Contributor: Contributors to the development of the digital standards or policy recommendations that are the output of this project.
  • Early Implementer: Supply chain actors or their software providers that wish to be early implementers of the standards defined by this project.

Scope & Areas of Focus​

Contributor activities have been scoped to ensure project deliverables add value, are not duplicative and are informed (by other related projects).

Technology interoperability standards​

  • Focus: Research and develop standards for technological interoperability between global CRM (Critical Raw Materials) supply chains.
  • Expertise required: Expertise in technological interoperability between supply chains, experience building open standards and contributing to interoperability solutions (i.e. blockchain or otherwise). Experience leading research projects related to verification, digital fingerprinting, traceability of materials within supply chains.

Sustainability criteria equivalency mapping standards​

  • Focus: To define how sustainability information criteria will be exchanged along the supply chain, developing an understanding of equivalency across borders and unique supply chain systems.
  • Expertise required: Expertise in the development of sustainability standards, mining performance certifications, and efforts focused on improving the overall sustainability and social impact of supply chains.

Legal/ethical considerations​

  • Focus: To understand legal and governance considerations related to supply chains, including audit/verification processes are connected and recognized across multiple jurisdictions. Scope will include
  • Legal enforcement of false claims
  • Mutual recognition of laws along the supply chain
  • Expertise required: Law professionals, especially those focusing on conflict of law on free trade agreements. Professionals with experience in privacy law, information sharing agreement law, and security of digital information regulatory compliance.

Implementation​

  • Focus: As standards are developed, the implementation pilots will test them along various supply chains (copper, graphite, lithium, cobalt).
  • Expertise required: Requires technical expertise to apply and integrate specific supply chain standards developed throughout the project into solutions/technology systems.

Working groups​

The Contributors working group consists of members who indicated their willingness to participate and have sufficient expertise. This working group will meet on a bi-weekly basis. Each area of focus will have an associated sub-working group, or workstream, with a lead. The leads will be selected from those who have indicated their interest using the following criteria:

  • Capability (must have sufficient domain knowledge to do the job)
  • Capacity (must be able to allocate sufficient time to do the job) and
  • Neutrality (must be acceptable as independent / non-competitive to all team members)

Workstreams will meet as needed in order to contribute meaningfully towards the development of draft deliverables. Workstream leads will report on their progress to the Contributors working group at the bi-weekly meeting. Workstreams (sub-groups) include:

  1. Traceability Interoperability - Zachary Zeus
  2. CRM Sustainability Claims Mapping - Kim Swanzey
  3. Implementation Pilot - Lithium supply chain originating in Australia - Prokopiy (Prok) Vasilyev
  4. Implementation Pilot - Copper supply chain originating in Canada - TBD
  5. Implementation Pilot - Cobalt supply chain originating in DRC - TBD
  6. Legal Analysis - Required for all workstreams - Dr. Jeanne Huang

Deliverables​

This project will deliver a suite of materials that support government policy makers, CRM industry actors, and traceability technology providers. The blue colured deliverables are expected to be re-usable across other supply chain domains such as garmets & footwear and agri-food. The yellow coloured deliverables are specific to the critical raw materials domain.

deliverables

Each deliverable is described on this website.

Criteria for assessing deliverables.​

  • Affordability : Affordability of the deliverable is defined as how many adopters along the supply chain are able to invest in and implement the recommendations without prohibitive cost.
  • Reliability : The standards and recommendations developed and implemented by this group must be reliable across different supply chain ecosystems and jurisdictions.
  • Accommodability: Deliverables are assessed on their ability to accommodate multiple supply chain solutions across jurisdictions through maintaining a technologically agnostic approach.
  • Scalability: Deliverables will be assessed based on their ability to scale across multiple jurisdictions, legal frameworks, regulatory environments, and technological limitations.
  • Alignment to SDGs: Deliverables will be assessed based on their alignment with the UN SDGs.
  • Privacy-preserving : Deliverables will be assessed on information security and privacy preserving characteristics.
  • Transparency-creating: Deliverables are assessed on their ability to further transparency and trust along supply chains.

Criteria for assessing implementation.​

The ultimate goal of this project is to facilitate the scalable uptake of digital traceability & transparency measures across the international supply chain. Delivery of standards is only a necessary milestone towards real production implementations. Therefore, this project will only be considered successful when:

  • at least 50 different CRM supply chain actors
  • using at least 5 different software platforms
  • across at least 5 different value chains
  • spanning at least 5 different countries
  • can reveal transparent supply chain evidence for at least 10,000 consignments

This is still a tiny fraction of actual global trade volumes but is deemed sufficient to prove that the framework is scalable.

Work plan, including activity schedules​

DeliverablesExpected timeline
Project Inceptionmonth 1
Call for participationmonth 1
Business requirements specificationsmonth 3 - 6
sustainability vocabulary, Credential schemamonths 4 - 8
Implementation guide, Test suitemonths 6 - 9
Pilots - engagementmonths 2 - 6
Pilots - implementationmonths 6 - 18
UN Policy recommendationdue month 12
Public Draft Reviewmonth 16 - 17
Project Exitmonth 18
- + \ No newline at end of file diff --git a/docs/deliverables/index.html b/docs/deliverables/index.html index eb987f68..1100116a 100644 --- a/docs/deliverables/index.html +++ b/docs/deliverables/index.html @@ -4,13 +4,13 @@ Project Delivery | Critical Raw Materials - +

Project Delivery

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Project Delivery

- + \ No newline at end of file diff --git a/docs/deliverables/management/index.html b/docs/deliverables/management/index.html index 897a324f..80015229 100644 --- a/docs/deliverables/management/index.html +++ b/docs/deliverables/management/index.html @@ -4,14 +4,14 @@ Project Management | Critical Raw Materials - +

Project Management

Call Schedule​

  • Workstream Leadership calls: Microsoft Teams Meeting Link; Meeting ID 229 018 415 830 and Passcode: NqSYnV
    • Traceability Interoperability Workstream: Zoom Meeting Link; Meeting ID: 811 2916 4487 and Passcode: 094449
    • Sustainability Vocabulary Mapping Workstream: TBA
    • Legal/Ethical Workstream: Zoom Meeting Link
    • Lithium (AUS) Pilot Implementation: TBA
    • Copper (CAN) Pilot Implementation: TBA
    • Cobalt (DRC) Pilot Implementation: TBA
- + \ No newline at end of file diff --git a/docs/pilots/CRM-requirements/index.html b/docs/pilots/CRM-requirements/index.html index 273c6647..66b1ef0e 100644 --- a/docs/pilots/CRM-requirements/index.html +++ b/docs/pilots/CRM-requirements/index.html @@ -4,14 +4,14 @@ CRM Traceability Requirements | Critical Raw Materials - +

CRM Traceability Requirements

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Introduction​

Some words about sustainability & resilience and the need for digital traceability and transparency. Greenwashing challenge & race to the top/ race to the bottom paths ahead

Document Purpose​

To provide the context and guide-rails for the pilot implementations in the CRM domain.

Audience​

The audience for this document include

RoleRationale
Mining operators
Refiners & manufacturers
ESG standards & certifiers
Software vendors
Regulators

Document Context​

TBA

Project Context​

Some words about how this project fit together with and complements other UN work

  • UN SDGs, criteria, indicators & tools. They are national level, our project is entity & product level.
  • Other UNECE traceability & transparency domains (textile & leather, agro-food). We build on common foundations.
  • UN/CEFACT trade vocabularies & standards – we use and, where necessary, extend them.
  • Industry standards (eg GS1 EPCIS) – we use established and relevant standards wherever they exist (so long as they are open & free) and do not re-invent them.
  • Global sustainability standards and regulations – we map them but do not re-invent them.

Design Principles​

Some words about key design principles. For example,

  • simple and implementable always wins over expansive & complex.
  • open and free is a fundamental requirement.
  • collaboratively developed encourages buy-in
  • decentralised over centralised will always be more scalable.

Design Challenges​

Some words about the key challenges that scalable digital traceability & transparency faces. The design must solve these challenges. For example

  • greenwashing
  • plethora of platforms – so we must focus on in interoperability, not picking winners.
  • plethora of standards – so we must focus on mapping between them to maximise reuse.

Scope​

Some words about the scope of this requirements document.

  • Critical Raw Materials supply chain business modelling (actors, processes, products, etc) for at least 3 minerals.
  • Extensions as necessary to traceability standards
  • Mappings as necessary for CRM standards & regulations.
  • Legal and ethical considerations (mutual recognition, disputes, etc)

The Critical Raw Materials Value Chain​

Setting out the language of the domain.

Actors​

List of actors – miners, processors, manufacturers, certifiers, etc Processes

General processes – mining, concentrate, refining, component manufacturing, finished product, lifetime of use, recycling.

Lithium​

Specifics for Lithium

Cobalt​

Specifics for Cobalt

Copper​

Specifics for Copper

Nickel​

Specifics for Nickel

Rare Earths​

Specifics for Rare Earths

EV Batteries​

Value chain from minerals to batteries (EV and household /community storage)

Solar Panels​

Value chain from minerals to solar panels (industrial generation and household)

Traceability Requirements​

Data Model​

Reference the generic traceability & transparency models and specify any extensions.

Vocabulary​

Reference the generic ESG vocabulary and specify CRM specific extensions.

Identifier Schemes​

Reference generic identifier schemes and specific any industry specific requirements.

Trust Anchors​

Identify Specific trust anchors for CRM domain

Sustainability Requirements​

ESG Standards & Regulations​

List standards and regulations relevant to the CRM sector. Including type categorisation

  • Industry standards (IRMA, TSM, etc )
  • Transnational initiatives (WEF GBA etc)
  • National regulations (EU DPP etc)

Vocabulary Mapping​

Requirements for mapping of criteria between standards and to UN vocabulary.

Reference generic legal toolkit and identify CRM specific concerns

- + \ No newline at end of file diff --git a/docs/pilots/Pilot-AUS/index.html b/docs/pilots/Pilot-AUS/index.html index c64da825..a4964e4f 100644 --- a/docs/pilots/Pilot-AUS/index.html +++ b/docs/pilots/Pilot-AUS/index.html @@ -4,13 +4,13 @@ Australian Lithium Pilot | Critical Raw Materials - +

Australian Lithium Pilot

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Australian Lithium Pilot

Key Focus​

This pilot focus is crotical mineral supply chain resilience and guarantee of origin / prevenance verification.

Stakeholders​

List pilot stakeholders here

Value chain​

Diagram the specific value chain(s) this pilot will implement.

Success criteria​

How will we know the pilot was successful?

- + \ No newline at end of file diff --git a/docs/pilots/Pilot-CAN/index.html b/docs/pilots/Pilot-CAN/index.html index fbefe271..ed48d976 100644 --- a/docs/pilots/Pilot-CAN/index.html +++ b/docs/pilots/Pilot-CAN/index.html @@ -4,13 +4,13 @@ Canadian Copper Pilot | Critical Raw Materials - +

Canadian Copper Pilot

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Canadian Copper Pilot

Key Focus​

This pilot focus is crotical mineral supply chain sustainability and environmental credentials verification.

Stakeholders​

List pilot stakeholders here

Value chain​

Diagram the specific value chain(s) this pilot will implement.

Success criteria​

How will we know the pilot was successful?

- + \ No newline at end of file diff --git a/docs/pilots/Pilot-DRC/index.html b/docs/pilots/Pilot-DRC/index.html index 77490502..cb36bacd 100644 --- a/docs/pilots/Pilot-DRC/index.html +++ b/docs/pilots/Pilot-DRC/index.html @@ -4,13 +4,13 @@ Congo Cobalt Pilot | Critical Raw Materials - +

Congo Cobalt Pilot

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Congo Cobalt Pilot

Key Focus​

This pilot focus is crotical mineral supply chain social & governance criteria (human welfare) and peer to peer trust models.

Stakeholders​

List pilot stakeholders here

Value chain​

Diagram the specific value chain(s) this pilot will implement.

Success criteria​

How will we know the pilot was successful?

- + \ No newline at end of file diff --git a/docs/pilots/index.html b/docs/pilots/index.html index 000dc966..06859793 100644 --- a/docs/pilots/index.html +++ b/docs/pilots/index.html @@ -4,13 +4,13 @@ CRM Supply Chain Pilots | Critical Raw Materials - +

CRM Supply Chain Pilots

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

- + \ No newline at end of file diff --git a/docs/standards/Interop-requirements/index.html b/docs/standards/Interop-requirements/index.html index 30956ddc..1c986426 100644 --- a/docs/standards/Interop-requirements/index.html +++ b/docs/standards/Interop-requirements/index.html @@ -4,13 +4,14 @@ Interoperability Requirements | Critical Raw Materials - +
-

Interoperability Requirements

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Introduction​

Some words about the need for digital traceability and the challenges about achieving it at scale.

Document Purpose​

To provide the context and guide-rails for the technical deliverables such as credential schema and traceability vocabularies

Audience​

The audience for this document include

RoleRationale
Mining operators
Refiners & manufacturers
ESG standards & certifiers
Software vendors
Regulators

Document Context​

TBA

Design Principles​

This document is guided by the following principles

  1. Simple and implementable always wins over expansive & complex.
  2. Open and free is a fundamental requirement.
  3. Collaborative development encourages buy-in
  4. Decentralised models will always be more scalable than centralised.

Design Challenges​

Implementating end-to-end supply chain traceability at scale faces a number of challenges.

ChallengeOur approach
A plethora of platforms exist alreadyWe must focus on in interoperability between systems, not picking winners.
Technology maturity is variableWe must accommodate small businesses and developing nations and allow a gradual transition from paper processes.
Most traceability pilots have not scaled to production volumesWe must design simple and scalable solutions that can be implemented at scale
Supply chain actors will not expose sensitve dataWe must allow stakeholders to protect sensitive commercial information whilst revealing ESG info.
ESG claims have different levels of trustWe must provide sufficient evidence to trust the claims.
Greenwashing fraud is endemicWe need to explicitly identify greenwashing fraud vectors and how to solve them – including product substation, mass balance, etc.
CostThe solution must be cheap enough that there remains plentiful margin incentive for producers and manufacturers to change behaviour.

Scope​

Digital Interoperability standards for scalable traceability & transparency

  • Supply chain events
  • entity, product & location identifiers
  • credential schema
  • privacy & security controls
  • linked data vocabularies

Traceability Interoperability Requirements​

Traceability Data Model​

This section should define a specific data model of the simplest possible EPCIS event structure and vocabulary that is just sufficient for end-to-end value chain traceability. Less is more because simple low cost implementation is key. Draw upon existing UN/CEFACT vocabulary.

Transparency Data Model​

This section should define the simplest possible data model for transparency information including

  • Sensors & measurements
  • Standards & Criteria
  • Audits & certificates
  • Accreditations & trust
  • Facilities, Equipment & capacity

Identifier Schemes​

This section should define prefered identity schemes for each type of identifier.

  • Legal entities (national authority schemes?)
  • Geographic locations (plus codes?)
  • Manufactured products (GTIN?)
  • Bulk product (?)
  • Manufacturing facility / equipment (Asset ID)

Verifiable Credentials​

This section should define VC interoperability profiles and DID methods so that the complexity of this space is simplified to a simple and implementable subset.

  • VC profiles - W3C SVIP, Hyperledger Aries,
  • DID methods for each identity type

Linked Credentials​

This section should define a standard profile for linked credentials – ie how multiple credentials are linked together to construct a trustworthy supply chain traceability view.

  • Link structure (target, type, role, etc)
  • Link integrity (eg issuer of credential is subject of linked credential etc)
  • Verifier behaviour (how to verify a graph of linked credentials as opposed to a single credential).

Trust Anchors​

Define methods by which trust & business integrity can be attached to ESG claims

  • Trust anchors - authoritative roots of trust such as governments & national accreditation authorities. Eg Guarantee of origin certificates.
  • Peer to peer - peer to peer trust networks (is community members keeping each other honest)

Privacy Model​

Define mechanisms to protect commercially sensitive information at any point in the value chain.

  • Document level security - encrypted storage and shared single use keys
  • Field level security - Selective redaction methods

Technology Maturity​

Designs to support stakeholders in the value chain that have zero technology maturity.

  • Human Rendering templates
  • QR links to hosted verifiers

Design solution to verifiably link the digital data to the physical shipment..

  • Finding ESG data from product ID using Digital Link resolvers
  • Doscovering the right resolver service

Provenance verification​

List known mechanisms for provenance verifiaction

  • Chemical / Istopic fingerprints

Sample Value Chain​

Draw a simplified example for lithium/Cobalt/Copper -> EV Battery -> recycling.

- +

Interoperability Requirements

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Introduction​

Traceability Interoperability for the Critical Raw Materials (CRM) industry has the opportunity to help consumers, manufacturers and miners share data up, down and across the supply chain in a consistent low cost way. We also seek to provide genuine accountability and the potential for independent validation of all types of claims in the supply chain.

Critical Raw Materials (CRM) are paramount to the functioning of our industrial ecosystems (digital, transport, construction, renewable energy technologies, lightweight batteries). They are essential for the green energy transition.(lithium in batteries, gallium and indium in LED lamps, and rare-earth elements in magnets for digital technologies, electric vehicles and wind generators.) Such elements derived from raw minerals are “critical” as they represent the most economically important source materials with high supply risk and they are concentrated in a few geographical areas. Additionally, The international CRM supply chain is growing in complexity at the same time as nation states seek to improve their border compliance for imports and facilitate access to export markets for their domestic producers. The global value chain is highly dependent on smooth cross-border supply flows (tangible, intangible and data).

There is a significant commercial shift occurring in the expectations for high quality, provable credentials for ESG activities and provenance validation. The companies that are able to demonstrate provable claims about their material sourcing and ESG activities will have easier access to markets and capital. The value of traceability interoperability is to drive down the cost of sharing and demonstrating high quality credentials for provenance claims and ESG activities. By providing standards for granular, provable claims that enable independent validation and assessment, companies that are genuinely in compliance will be easily distinguished from those that cannot be validated.

Document Purpose​

The purpose of this document is to define the requirements for traceability interoperability. +This work stream is intended to answer the “How” for data exchange and the sustainability working group is answering the “What” data to exchange.

This document also provides the context and guide-rails for the technical deliverables for the CRM pilots such as credential schema and traceability vocabularies to drive the adoption of traceability standards that enable verifiable claims.

Audience​

The primary audience for this document include the following:

RoleRationale
Mining operatorsThe mining operators are the start of the value chain and for the operators that are generating the origin claims and investing in ESG activities it will be important that they can provably demonstrate their activities so that they can access markets and capital that value those investments in ESG outcomes.
Refiners & manufacturersThe key challenges we’ll be focusing on for refiners and manufacturers will be how they demonstrate the provenance claims and ESG features of the inputs to the products that they produce and how the credentials about those inputs are 'attached' to the goods that they are producing.
ESG standards & certifiersThe value of the standard and/or certifications are tied directly to the value the market places of having a trustable proof that the good or services meets the standard. A verifiable certificate provides this proof. The certification and accreditation community create an important trust anchor.
Software vendorsSharing digital credentials about the material origin and ESG of data of the CRM industry is going to be powered by the digital tools that members of the supply chain use. This paper is intended to articulate how software vendors can extend their existing infrastructure in a low cost and scalable manner to support the industry.
Government organizationswhen governments subsidise the critical minerals for strategic or national interest purposes, proof that the national interest has been met could be provided by leveraging verifiable certificate that provides the proof of the benefit.
RegulatorsRegulators play a unique role in any value chain. They can be a trust anchor that helps their regulated community outcompete in a global marketplace. However, regulators require traceability in order to be effective. This paper will highlight principles to enable regulators to require verifiable and enforceable standards, by providing a model to corroborate and authenticate claims effectively.
PeopleImpacts on people are generally the fundamental driver of regulatory standards. By having an avenue to weigh in on the validation process of claims, people impacted can have some leverage to ensure that regulations are followed in alignment with their original purpose. By providing evidence driven pathways for people to participate, it may be that conflicts of interest can be channeled productively into evidence gathering.

Document Context​

The focus of this document is traceability interoperability of the critical raw materials industry. In addition there is parallel work going in in Recommendation 49 about transparency at scale that this document will inform and we will seek guidance from. It is important that traceability interoperability works for the CRM industry in the same way as it works in adjacent and upstream industries.

Design Principles​

This document is guided by the following principles

  1. Simple and implementable always wins over expansive & complex.
  2. Open and free is a fundamental requirement.
  3. Collaborative development encourages buy-in
  4. Decentralised models will always be more scalable than centralised.
  5. Independently verifiable claims are more credible.
  6. Learn and leverage from existing ecosystems, methodologies, standards and approaches.

Design Challenges​

Implementing end-to-end supply chain traceability at scale faces a number of challenges.

ChallengeOur approach
A plethora of platforms exist alreadyWe must focus on interoperability between systems, not picking winners. We’ll also provide guidance on how existing systems can extend their capability to support interoperability.
Technology maturity is variableWe must accommodate small businesses and developing nations and allow a gradual transition from paper processes.
Most traceability pilots have not scaled to production volumesWe must design simple and scalable solutions that can be implemented at scale
Supply chain actors will not expose sensitive dataWe must allow stakeholders to protect sensitive commercial information whilst revealing ESG info.
ESG claims have different levels of trustWe must provide sufficient evidence to trust the claims.
Greenwashing fraud is endemicWe need to explicitly identify greenwashing fraud vectors and how to solve them – including product substation, mass balance, etc. In particular in CRM, suppliers have taken the approach of inserting a middleman and obscuring the traceability to the source. A goal of this approach must be the traceability of claims back to the point of extraction, as required by the OECD due diligence handbook.
CostThe solution must be cheap enough that there remains plentiful margin incentive for producers and manufacturers to change behaviour.

Scope​

Digital Interoperability standards for scalable traceability & transparency

  • Supply chain events
  • Entity, product, process, time & location identifiers
  • Credential schema
  • Privacy & security controls
  • Linked data vocabularies

NOTE: from here down has not been updated as of Oct 30th 2023. Updates are expected by Nov 21st 2023.

Traceability Interoperability Requirements​

Traceability Data Model​

This section should define a specific data model of the simplest possible EPCIS event structure and vocabulary that is just sufficient for end-to-end value chain traceability. Less is more because simple low cost implementation is key. Draw upon existing UN/CEFACT vocabulary.

Transparency Data Model​

This section should define the simplest possible data model for transparency information including

  • Sensors & measurements
  • Standards & Criteria
  • Audits & certificates
  • Accreditations & trust
  • Facilities, Equipment & capacity

Identifier Schemes​

This section should define prefered identity schemes for each type of identifier.

  • Legal entities (national authority schemes?)
  • Geographic locations (plus codes?)
  • Manufactured products (GTIN?)
  • Bulk product (?)
  • Manufacturing facility / equipment (Asset ID)

Verifiable Credentials​

This section should define VC interoperability profiles and DID methods so that the complexity of this space is simplified to a simple and implementable subset.

  • VC profiles - W3C SVIP, Hyperledger Aries,
  • DID methods for each identity type

Linked Credentials​

This section should define a standard profile for linked credentials – ie how multiple credentials are linked together to construct a trustworthy supply chain traceability view.

  • Link structure (target, type, role, etc)
  • Link integrity (eg issuer of credential is subject of linked credential etc)
  • Verifier behaviour (how to verify a graph of linked credentials as opposed to a single credential).

Trust Anchors​

Define methods by which trust & business integrity can be attached to ESG claims

  • Trust anchors - authoritative roots of trust such as governments & national accreditation authorities. Eg Guarantee of origin certificates.
  • Peer to peer - peer to peer trust networks (is community members keeping each other honest)

Privacy Model​

Define mechanisms to protect commercially sensitive information at any point in the value chain.

  • Document level security - encrypted storage and shared single use keys
  • Field level security - Selective redaction methods

Technology Maturity​

Designs to support stakeholders in the value chain that have zero technology maturity.

  • Human Rendering templates
  • QR links to hosted verifiers

Design solution to verifiably link the digital data to the physical shipment..

  • Finding ESG data from product ID using Digital Link resolvers
  • Doscovering the right resolver service

Provenance verification​

List known mechanisms for provenance verifiaction

  • Chemical / Istopic fingerprints

Sample Value Chain​

Draw a simplified example for lithium/Cobalt/Copper -> EV Battery -> recycling.

+ \ No newline at end of file diff --git a/docs/standards/impelemntation-guidance/index.html b/docs/standards/impelemntation-guidance/index.html index 0d465c84..bc781607 100644 --- a/docs/standards/impelemntation-guidance/index.html +++ b/docs/standards/impelemntation-guidance/index.html @@ -4,13 +4,13 @@ Implementation Guidance | Critical Raw Materials - +

Implementation Guidance

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Guidance for software developers that will implement the traceability interoperability specifications.

- + \ No newline at end of file diff --git a/docs/standards/index.html b/docs/standards/index.html index d8e3d625..46cd5631 100644 --- a/docs/standards/index.html +++ b/docs/standards/index.html @@ -4,13 +4,13 @@ Interoperability Standards | Critical Raw Materials - +

Interoperability Standards

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

- + \ No newline at end of file diff --git a/docs/standards/traceability-schema/index.html b/docs/standards/traceability-schema/index.html index 6ac9e865..0d52f369 100644 --- a/docs/standards/traceability-schema/index.html +++ b/docs/standards/traceability-schema/index.html @@ -4,13 +4,13 @@ Traceability Schema | Critical Raw Materials - +

Traceability Schema

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

EPCIS based traceability schema links go here

- + \ No newline at end of file diff --git a/docs/standards/transparency-schema/index.html b/docs/standards/transparency-schema/index.html index 3acd338c..094a760b 100644 --- a/docs/standards/transparency-schema/index.html +++ b/docs/standards/transparency-schema/index.html @@ -4,13 +4,13 @@ Transparency Schema | Critical Raw Materials - +

Transparency Schema

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Certificate, sensor measurement, equipment schema links go here

- + \ No newline at end of file diff --git a/docs/vocabulary/index.html b/docs/vocabulary/index.html index 62488da9..31eab1a7 100644 --- a/docs/vocabulary/index.html +++ b/docs/vocabulary/index.html @@ -4,13 +4,13 @@ Core Vocabulary | Critical Raw Materials - +

Core Vocabulary

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

- + \ No newline at end of file diff --git a/docs/vocabulary/legal-toolkit/index.html b/docs/vocabulary/legal-toolkit/index.html index 99f5bc7c..499e9e0c 100644 --- a/docs/vocabulary/legal-toolkit/index.html +++ b/docs/vocabulary/legal-toolkit/index.html @@ -4,13 +4,13 @@ Legal toolkit | Critical Raw Materials - +

Legal toolkit

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Legal framework for mutual recognition / compliance management

- + \ No newline at end of file diff --git a/docs/vocabulary/vocabulary-requirements/index.html b/docs/vocabulary/vocabulary-requirements/index.html index 9c011d2b..e2a13be9 100644 --- a/docs/vocabulary/vocabulary-requirements/index.html +++ b/docs/vocabulary/vocabulary-requirements/index.html @@ -4,13 +4,13 @@ Vocabulary Requirements | Critical Raw Materials - +

Vocabulary Requirements

info

Please note that this content is under development and is not ready for implementation. This status message will be updated as content development progresses.

Introduction​

Some words about the plethora of standards & regulations and the need for some shared understanding and mutual recognition, particularly in the cross border context.

Document Purpose​

To provide the context and guide-rails for the deliverables including sustainability vocabularies and legal / ethical guidelines.

Audience​

The following stakeholders will be interested in this document

RoleRationale
Mining operators
Refiners & manufacturers
ESG standards & certifiers
Software vendors
Regulators

Document Context​

TBA

Design Principles​

This document is guided by the following principles

  1. Simple and implementable always wins over expansive & complex.
  2. Open and free is a fundamental requirement.
  3. Collaborative development encourages buy-in
  4. We cant change existing standards & regulations, only map between them.

Design Challenges​

Implementating end-to-end supply chain transparency at scale faces a number of challenges.

ChallengeOur approach
A plethora of standards exist alreadyWe must focus on mapping between standards, not picking winners.
Regulations are emerging nearly as fastWe must focus on mutual recognition arrangements so that compliance in an exporting jusrisdication can be re-used by importing jurisdictions.
Complexity is overwhelmingConsumers and buyers cant be expected to understand every criteria of every standard or regulation and so we must focus on simple aggregated scoring
Involuntary non-compliance is likely to be highWe must find simple legal toolkits to support supply chain actors and regulators in managing involutary non-compliance.
Sustainment CostManually managing mapping between thousands of standards & criteria is likely to be un-sustainable so we should look to AI for help.

Scope​

In scope

  • ESG criteria vocabulary
  • Mapping tools and methods
  • Legal toolkit

Requirements​

Standards & Regulations​

Some words about relevant ESG standards and regulations as well as emerging initiatives

  • Industry standards (IRMA, TSM, etc )
  • Transnational initiatives (WEF GBA etc)
  • National regulations (EU DPP etc)

UN Core Vocabulary​

Assessment of various standards and mapping to UN core

  • A core sustainability vocabulary
  • How to map to the vocabulary
  • Aggregation (view) of the vocabulary to SDGs

Vocabulary Governance​

Mechanisms for long term maintenance of the core vocabulary and tools for ongoing mapping of ESG standards and regulatory frameworks.

Criteria Mapping​

Mechanisms to map claims from one standard to criteria of another.

Legal & Ethical Considerations​

Types of Standards​

Some words about the governance patterns of various standards (who, why, etc).

Types of Audit & Verification​

Some words about different types of verification and trust levels attached to each.

  • Self-assessment / peer group
  • On site instrumentation & measurement
  • Third party audit & certification
  • Funding models (who pays for audits)
  • Transparency models (audit and/or measurements are public/private)

Some words about legal considerations of mapping criteria

  • Self-assessed mapping and liabilitiy
  • Third party assessed mapping (who’s liable if wrong?)
  • Formal one-way recognition
  • Formal mutual recognition
- + \ No newline at end of file diff --git a/index.html b/index.html index b545c6fc..de5b40ca 100644 --- a/index.html +++ b/index.html @@ -4,13 +4,13 @@ United Nations - Critical Raw Materials | Critical Raw Materials - +

Critical Raw Materials

Scaling traceability and transparency through decentralisation and digital standards

Join our chat channel
Group 16
CRM Producers Icon

CRM Producers and manufacturers

Participate in global CRM traceability and be able to re-use your domestic ESG claims in export markets.

ESG Standard

ESG standards and certifiers

Map your ESG crtieria to a harmonised vocabulary and empower mutual recognition against other standards.

ESG Traceability Software

ESG Traceability software platforms

Align with interoperability standards and empower your customers to exchange ESG credentials up and down their supply chain.

- + \ No newline at end of file diff --git a/privacy/index.html b/privacy/index.html index a2eca73d..7ec3e2ae 100644 --- a/privacy/index.html +++ b/privacy/index.html @@ -4,13 +4,13 @@ Privacy | Critical Raw Materials - +

Privacy

By accessing this site, certain information about the User, such as Internet protocol (IP) addresses, navigation through the Site, the software used and the time spent, along with other similar information, will be stored on United Nations servers. These will not specifically identify the User.

The information will be used internally only for web site traffic analysis. If the User provides unique identifying information, such as name, address and other information on forms stored on this Site, such information will be used only for statistical purposes and will not be published for general access. The United Nations, however, assumes no responsibility for the security of this information.

- + \ No newline at end of file diff --git a/terms/index.html b/terms/index.html index d33d1fa9..172d85f1 100644 --- a/terms/index.html +++ b/terms/index.html @@ -4,13 +4,13 @@ Terms and Conditions | Critical Raw Materials - +

Terms

The use of this web site constitutes agreement with the following terms and conditions:

(a) The United Nations maintains this web site (the “Site”) as a courtesy to those who may choose to access the Site (“Users”). The information presented herein is for informative purposes only. The United Nations grants permission to Users to visit the Site and to download and copy the information, documents and materials (collectively, “Materials”) from the Site for the User’s personal, non-commercial use, without any right to resell or redistribute them or to compile or create derivative works therefrom, subject to the terms and conditions outlined below, and also subject to more specific restrictions that may apply to specific Material within this Site.

(b) The United Nations administers this Site. All Material on this Site from the United Nations appears subject to the present Terms and Conditions.

(c) Unless expressly stated otherwise, the findings, interpretations and conclusions expressed in the Materials on this Site are those of the various United Nations staff members, consultants and advisers to the United Nations Secretariat who prepared the work and do not necessarily represent the views of the United Nations or its Member States.

Disclaimers​

Materials provided on this Site are provided “as is”, without warranty of any kind, either express or implied, including, without limitation, warranties of merchantability, fitness for a particular purpose and non-infringement. The United Nations specifically does not make any warranties or representations as to the accuracy or completeness of any such Materials. The United Nations periodically adds, changes, improves or updates the Materials on this Site without notice. Under no circumstances shall the United Nations be liable for any loss, damage, liability or expense incurred or suffered that is claimed to have resulted from the use of this Site, including, without limitation, any fault, error, omission, interruption or delay with respect thereto. The use of this Site is at the User’s sole risk. Under no circumstances, including but not limited to negligence, shall the United Nations or its affiliates be liable for any direct, indirect, incidental, special or consequential damages, even if the United Nations has been advised of the possibility of such damages.

The User specifically acknowledges and agrees that the United Nations is not liable for any conduct of any User.

This site may contain advice, opinions and statements of various information providers. The United Nations does not represent or endorse the accuracy or reliability of any advice, opinion, statement or other information provided by any information provider, any User of this Site or any other person or entity. Reliance upon any such advice, opinion, statement, or other information shall also be at the User’s own risk. Neither the United Nations nor its affiliates, nor any of their respective agents, employees, information providers or content providers, shall be liable to any User or anyone else for any inaccuracy, error, omission, interruption, deletion, defect, alteration of or use of any content herein, or for its timeliness or completeness, nor shall they be liable for any failure of performance, computer virus or communication line failure, regardless of cause, or for any damages resulting therefrom.

As a condition of use of this Site, the User agrees to indemnify the United Nations and its affiliates from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys’ fees) arising out of the User’s use of this Site, including, without limitation, any claims alleging facts that if true would constitute a breach by the User of these Terms and Conditions. If the User is dissatisfied with any Material on this Site or with any of its Terms and Conditions of Use, the User’s sole and exclusive remedy is to discontinue using the Site.

This Site may contain links and references to third-party web sites. The linked sites are not under the control of the United Nations, and the United Nations is not responsible for the content of any linked site or any link contained in a linked site. The United Nations provides these links only as a convenience, and the inclusion of a link or reference does not imply the endorsement of the linked site by the United Nations.

If this Site contains bulletin boards, chat rooms, access to mailing lists or other message or communication facilities (collectively, “Forums”), the User agrees to use the Forums only to send and receive messages and materials that are proper and related to the particular Forum. By way of example and not as a limitation, the User agrees that when using a Forum, he or she shall not do any of the following:

(a) Defame, abuse, harass, stalk, threaten or otherwise violate the legal rights (such as rights of privacy and publicity) of others;

(b) Publish, post, distribute or disseminate any defamatory, infringing, obscene, indecent or unlawful material or information;

(c) Upload or attach files that contain software or other material protected by intellectual property laws (or by rights of privacy and publicity) unless the User owns or controls the rights thereto or has received all consents therefor as may be required by law;

(d) Upload or attach files that contain viruses, corrupted files or any other similar software or programs that may damage the operation of another’s computer;

(e) Delete any author attributions, legal notices or proprietary designations or labels in any file that is uploaded;

(f) Falsify the origin or source of software or other material contained in a file that is uploaded;

(g) Advertise or offer to sell any goods or services, or conduct or forward surveys, contests or chain letters, or download any file posted by another user of a Forum that the User knows, or reasonably should know, cannot be legally distributed in such manner.

The User acknowledges that all Forums and discussion groups are public and not private communications. Further, the User acknowledges that chats, postings, conferences, e-mails and other communications by other Users are not endorsed by the United Nations, and that such communications shall not be considered to have been reviewed, screened or approved by the United Nations. The United Nations reserves the right to remove, for any reason and without notice, any content of the Forums received from Users, including, without limitation, e-mail and bulletin board postings.

Preservation of immunities​

Nothing herein shall constitute or be considered to be a limitation upon or a waiver of the privileges and immunities of the United Nations, which are specifically reserved.

General​

The United Nations reserves its exclusive right in its sole discretion to alter, limit or discontinue the Site or any Materials in any respect. The United Nations shall have no obligation to take the needs of any User into consideration in connection therewith.

The United Nations reserves the right to deny in its sole discretion any user access to this Site or any portion thereof without notice.

No waiver by the United Nations of any provision of these Terms and Conditions shall be binding except as set forth in writing and signed by its duly authorized representative.

- + \ No newline at end of file