From fdc6d8e5568c3efcbf81141f3fa4b9fa163cd6b1 Mon Sep 17 00:00:00 2001 From: Steven Capell Date: Tue, 7 Jan 2025 13:54:22 +1100 Subject: [PATCH] Refactor CRMTP site To align with AATP site and establish a UNTP extensions convention. --- .../business-case/BusinessCaseTemplates.md | 20 ++++++ website/docs/business-case/CaseStudies.md | 34 +++++++++ .../CostBenefitModel.png | Bin website/docs/business-case/index.md | 6 ++ website/docs/guidance/Cobalt.md | 47 ++++++++++++ website/docs/guidance/Copper.md | 54 ++++++++++++++ website/docs/guidance/Lithium.md | 47 ++++++++++++ website/docs/guidance/Nickel.md | 47 ++++++++++++ website/docs/guidance/index.md | 4 +- website/docs/guidance/reference.md | 14 ---- website/docs/guidance/stages.md | 67 ------------------ website/docs/guidance/testing.md | 7 +- website/docs/register/index.md | 2 +- website/docs/resources/business-case.md | 16 ----- .../docs/resources/community-activation.md | 10 --- website/docs/resources/index.md | 6 -- website/docs/resources/value-assessment.md | 11 --- .../specification/DigitalTraceabilityEvent.md | 47 ++++++++++++ website/docs/specification/index.md | 2 +- website/docusaurus.config.js | 6 +- 20 files changed, 315 insertions(+), 132 deletions(-) create mode 100644 website/docs/business-case/BusinessCaseTemplates.md create mode 100644 website/docs/business-case/CaseStudies.md rename website/docs/{resources => business-case}/CostBenefitModel.png (100%) create mode 100644 website/docs/business-case/index.md create mode 100644 website/docs/guidance/Cobalt.md create mode 100644 website/docs/guidance/Copper.md create mode 100644 website/docs/guidance/Lithium.md create mode 100644 website/docs/guidance/Nickel.md delete mode 100644 website/docs/guidance/reference.md delete mode 100644 website/docs/guidance/stages.md delete mode 100644 website/docs/resources/business-case.md delete mode 100644 website/docs/resources/community-activation.md delete mode 100644 website/docs/resources/index.md delete mode 100644 website/docs/resources/value-assessment.md create mode 100644 website/docs/specification/DigitalTraceabilityEvent.md diff --git a/website/docs/business-case/BusinessCaseTemplates.md b/website/docs/business-case/BusinessCaseTemplates.md new file mode 100644 index 00000000..480939a0 --- /dev/null +++ b/website/docs/business-case/BusinessCaseTemplates.md @@ -0,0 +1,20 @@ +--- +sidebar_position: 5 +title: Business Case Templates +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + + +## Cost Benefit Modeling Template + +The spreadsheet template below provides a very simple tool to assist with the first-pass estimate of CRMTP implementation costs and benefits for individual businesses. It allows the user to choose how to weight each benefit category to suit their own circumstances. It also allows users to model break-even point with different assumptions about uptake rate across trading partners. + +**Spreadsheet model TBD** + + + + + diff --git a/website/docs/business-case/CaseStudies.md b/website/docs/business-case/CaseStudies.md new file mode 100644 index 00000000..203d4f28 --- /dev/null +++ b/website/docs/business-case/CaseStudies.md @@ -0,0 +1,34 @@ +--- +sidebar_position: 10 +title: Case Studies +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Summary + +|Case Study|Date|Summary| +|--|--|--| +|[BC Government Mines Permit](#bc-government-mines-permit)|Aug-Dec 2023|Verified usability of the UNTP Digital Conformity Credential as the basis for a regulatory permit.| +|[Mining Association of Canada - TSM credential](#mining-association-of-canada-tsm-credential) |Jan-Apr 2024 | Verified usability of the UNTP Digital Conformity Credential as the basis for a mine ststainability certificate.| + + + +### BC Government Mines Permit + +Some words about mines permit + +* Participants were.. +* Technical deliverables were.. +* Outcomes were.. + + +### Mining Association of Canada TSM Credential + +Some words about TSM + +* Participants were.. +* Technical deliverables were.. +* Outcomes were.. \ No newline at end of file diff --git a/website/docs/resources/CostBenefitModel.png b/website/docs/business-case/CostBenefitModel.png similarity index 100% rename from website/docs/resources/CostBenefitModel.png rename to website/docs/business-case/CostBenefitModel.png diff --git a/website/docs/business-case/index.md b/website/docs/business-case/index.md new file mode 100644 index 00000000..0a50cff4 --- /dev/null +++ b/website/docs/business-case/index.md @@ -0,0 +1,6 @@ +--- +sidebar_position: 10 +title: Business Case +--- + + diff --git a/website/docs/guidance/Cobalt.md b/website/docs/guidance/Cobalt.md new file mode 100644 index 00000000..b6ed032c --- /dev/null +++ b/website/docs/guidance/Cobalt.md @@ -0,0 +1,47 @@ +--- +sidebar_position: 10 +title: Cobalt +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Cobalt Value Chain + +The cobalt value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. + +diagram goes here + +Any actor that has an identifier of a cobalt product, minsite, or refinery can find the issued credentials and verify them. In general, downstream actors will be verifiers of upstream credentials. + +## Implementation Guidance + +Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. + +|Role|Issuer of|Comments| +|--|--|--| +|Mine site|cobalt passport|comments | +|Certifier |cobalt credential| | +|Regulator|Mine Permit| | +|etc| | | + + +## Identity Anchors + + +|Role|Identity Anchor Type|Comment| +|--|--|--| +| | | | + + + + +TBD + + + + + + + diff --git a/website/docs/guidance/Copper.md b/website/docs/guidance/Copper.md new file mode 100644 index 00000000..4b4f6ed2 --- /dev/null +++ b/website/docs/guidance/Copper.md @@ -0,0 +1,54 @@ +--- +sidebar_position: 10 +title: Copper +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Copper Value Chain + +The copper value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. + +diagram goes here + +Any actor that has an identifier of a copper product, minsite, or refinery can find the issued credentials and verify them. In general, downstream actors will be verifiers of upstream credentials. + +## Implementation Guidance + +Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the AATP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. + +|Role|Issuer of|Comments| +|--|--|--| +|Mine site|Copper passport|comments | +|Certifier |CopperMark credential| | +|Regulator|Mine Permit| | +|etc| | | + + +## Identity Anchors + +Identity anchors add increased trust to the CRMTP ecosystem because they link the DIDs (Self-issued IDs) of actors such as miners and refiners to authoritative registers such as Business registers. They are very simple credentials and are simple to issue. Their purpose and detailed implementation guidance are provided in the UNTP [Digital Identity Anchor (DIA)](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor) specification. The DIA is mapped to CRMTP identifiers in the [Identifiers](../specification/Identifiers) section of this website. The table below lists the specific identity anchors relevant for actors in the industry. Each actor SHOULD request the corresponding identity credential from their registrar and should make it discoverable by + +* linking it to their DID `serviceEndpoint` as described in [DIA DID discovery](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor#via-did-service-endpoint) +* adding it to their registry entry as a link type as described in [DIA Resolver Discovery](https://uncefact.github.io/spec-untp/docs/specification/DigitalIdentityAnchor#via-identity-resolver) + +These tasks will normally be facilitated by the registrar such as the national business register. + +|Role|Identity Anchor Type|Comment| +|--|--|--| +| | | | + + +## Buyers (Retailers & Brands) + + +TBD + + + + + + + diff --git a/website/docs/guidance/Lithium.md b/website/docs/guidance/Lithium.md new file mode 100644 index 00000000..3d08c723 --- /dev/null +++ b/website/docs/guidance/Lithium.md @@ -0,0 +1,47 @@ +--- +sidebar_position: 12 +title: Lithium +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Lithium Value Chain + +The lithium value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. + +diagram goes here + +Any actor that has an identifier of a lithium product, minsite, or refinery can find the issued credentials and verify them. In general, downstream actors will be verifiers of upstream credentials. + +## Implementation Guidance + +Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. + +|Role|Issuer of|Comments| +|--|--|--| +|Mine site|Lithium passport|comments | +|Certifier |Lithium credential| | +|Regulator|Mine Permit| | +|etc| | | + + +## Identity Anchors + + +|Role|Identity Anchor Type|Comment| +|--|--|--| +| | | | + + + + +TBD + + + + + + + diff --git a/website/docs/guidance/Nickel.md b/website/docs/guidance/Nickel.md new file mode 100644 index 00000000..6c0491d9 --- /dev/null +++ b/website/docs/guidance/Nickel.md @@ -0,0 +1,47 @@ +--- +sidebar_position: 10 +title: Nickel +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Nickel Value Chain + +The nickel value chain shown below indicates which role(s) are expected to **issue** which CRMTP credential types. + +diagram goes here + +Any actor that has an identifier of a nickel product, minsite, or refinery can find the issued credentials and verify them. In general, downstream actors will be verifiers of upstream credentials. + +## Implementation Guidance + +Each implementer role should follow links to the relevant credential specifications and ensure that they are issuing credentials according to the relevant specification. In most cases the technical implementation will be done by underlying [software](../register/Software) systems. However it is still important that each actor confirm that the CRMTP credentials issued by their chosen systems are valid by dropping them into the [conformity testing](Testing) service. + +|Role|Issuer of|Comments| +|--|--|--| +|Mine site|Nickel passport|comments | +|Certifier |Nickel credential| | +|Regulator|Mine Permit| | +|etc| | | + + +## Identity Anchors + + +|Role|Identity Anchor Type|Comment| +|--|--|--| +| | | | + + + + +TBD + + + + + + + diff --git a/website/docs/guidance/index.md b/website/docs/guidance/index.md index 68a04994..d1c3a19e 100644 --- a/website/docs/guidance/index.md +++ b/website/docs/guidance/index.md @@ -1,6 +1,6 @@ --- -sidebar_position: 20 -title: Guidance for Implementers +sidebar_position: 15 +title: Guidance --- import Disclaimer from '../\_disclaimer.mdx'; diff --git a/website/docs/guidance/reference.md b/website/docs/guidance/reference.md deleted file mode 100644 index 4982decc..00000000 --- a/website/docs/guidance/reference.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -sidebar_position: 30 -title: Test Implementation ---- - -import Disclaimer from '../\_disclaimer.mdx'; - - - -Test implementations assist individual implementers and communities of implementers to test your conformance with UNTP-CRM, prior to broad adoption. -These tools allow early implementers to manually create trial digital credentials, and publish them so they can be accessed by other pilot implementers, such as trading partners, customs authorities, and investors. You can find other planned implementers here, with whom you can test your test implementation. - -* A description of tools for undertaking a test implementation can be found at the [UNTP site](https://uncefact.github.io/tests-untp/). -* The tools and guidance for their use can be accessed [here](https://uncefact.github.io/tests-untp/docs/mock-apps/). diff --git a/website/docs/guidance/stages.md b/website/docs/guidance/stages.md deleted file mode 100644 index 92e4648c..00000000 --- a/website/docs/guidance/stages.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -sidebar_position: 5 -title: Stages of Implementation ---- - -import Disclaimer from '../\_disclaimer.mdx'; - - - -![D4.1Timeline](../files/D4.1Timeline.png) - -## First Stage: Early Implementation (“crawl”) - -### **Familiarize Yourself with UNTP-CRM’s Core Concepts** - -We suggest you familiarize yourself with the core concepts listed in the [UNTP Architecture](https://uncefact.github.io/spec-untp/docs/specification/), including how they are applied in the [CRM context](https://uncefact.github.io/project-crm/docs/specification/Architecture). We also suggest you read the [Implementers section](https://uncefact.github.io/project-crm/docs/register/) of this site to understand the various roles, and consider which role your organization would play as an UNTP-CRM implementer. - -### **Declare your Interest** - -State your interest in participation to the project team using [this form](https://docs.google.com/forms/d/e/1FAIpQLSecdZ4izTK-K64NA53grzmjIEJ26Y-yLjpm-2G_28ICzVk0zQ/viewform?usp=pp_url). We will follow up with you to assess your suitability for early implementation, and assist you to define your scope and value proposition. - -### **Define Your Scope and Value Proposition** - -Based on our interactions with potential early implementers, we’ve observed a typical engagement pattern, in which an interested party within an organization reaches out to the project team regarding participation as an implementer, and requires additional information about **1) resources required and 2) value of participation**. Armed with this information, they can advocate for participation to other relevant decision makers within their organization, such as their sustainability, IT and supply chain leads. - -With this in mind, we have developed a [**value proposition template**](https://docs.google.com/presentation/d/1CXkunB9L5Nr-Xw-4tQ8rJOYNMOZOObF7/edit?usp=sharing&ouid=102588425343518355761&rtpof=true&sd=true) to assist potential implementers in articulating the benefits of participation and resources required for their organization. As you develop your value proposition, we suggest you map your community, using the recommendations below, as the value of early implementation will increase when multiple parties can share verified data interoperability. - -We also recommend that you start to develop an implementation plan and business case for your “Walk”/Alpha phase implementation. Based on our research into relevant funding programs, such as CIRPASS 2, they are looking for consortiums that are post-pilot, implementation-ready. Consider activating your community/ supply chain as you undertake early implementation to realize full value and prepare for external funding applications. - -### **Map and Activate Your Community** - -As the UNTP-CRM defines a scalable methodology for data sharing among CRM industry actors along supply chains, the value of implementation is only realized through adoption by multiple actors: - -* For **supply chain actors**, it is beneficial to identify who you buy and sell to, and assess whether they would like to join you as an early implementer, to increase the value of your participation. See the [UNTP Community Activation page](https://uncefact.github.io/spec-untp/docs/business-case/CommunityActivationProgram) for suggested approaches. The UNTP-CRM team can assist with connecting you to other CRM industry actors who have expressed interest in early implementation and could benefit from a collaborative, multi-stakeholder pilot. -* For **regulators**, performance certifiers, and assurance providers, can increase the value of certifications, permits, and audit reports by enabling them to be digitally linked to product-level claims. By activating the organizations you certify, regulate and audit to become UNTP-CRM implementers, you can add a new dimension of utility to your outputs. -* For **software providers**, sharing digital credentials about the material origin and ESG data of CRM shipments is going to be powered by the digital tools. Technology platforms that are compatible with other platforms offer higher value to customers who need to exchange credentials internationally. Activating your community and customers to become UNTP-CRM compliant increases the value of the service you provide. - -You can find advice and best practices on the [UNTP community activation page](https://uncefact.github.io/spec-untp/docs/business-case/CommunityActivationProgram) to help identify and engage other actors in your ecosystem including your upstream suppliers, downstream customers, conformity assessment bodies, and traceability software vendors. As early implementers progress to full adoption, they can provide feedback to the CRM project team to develop and refine CRM-specific community activation guidance and tools. - -### **Identify the Sustainability Information Requested by Your Buyers and Sellers** - -For supply chain actors, such as mining companies, smelters, processors and manufacturers, we suggest you identify the sustainability information that you are being asked for by your buyers and sellers. This will inform the design of the digital product passport you will publish for shipments of your goods. - -As part of the implementation testing phase, the Project Team has created [this short survey](https://docs.google.com/forms/d/1E1-kRuP3FDkxhamXbTRixhWA5xifyvqKxkzgSaYOjhE/prefill) (15 minutes) which will ask participants to select from a set of ESG criteria, indicating the information they are most often asked to provide to buyers and sellers. The Project Team will follow up with willing respondents for a 30-60 minute information interview. Survey and interview results will assist in the refinement of a finalized sustainability criteria list, which can be used by implementers to design their digital product passports. - -### **Create and Register Your Test Implementation** - -* Manually create trial digital credentials and exchange with a small number of trading partners. -* If you have an IT department, ask them to review the Technical Specification, Reference Implementation and Conformity Testing sections of this website. They can determine whether they have the in-house capability and capacity to undertake and test a UNTP-CRM test implementation. The Project Team would be happy to meet with you and discuss this. -* Consider working with a Traceability Solution provider that is either UNTP-compliant or is working to become UNTP-compliant. The Project Team can facilitate introductions as requested. - -### **Create a Business Case to Proceed to Alpha Phase** - -## Second Stage: Implementation (“walk”) - -* Undertake Community Activation Plan and Designate Community Leader. -* Validate integration cost & complexity. -* Validate of scope and value. -* Automate the creation and verification of digital credentials from your own business systems (in test environments). -* Engage with the activated community to achieve consistency in implementation across a commodity and/or geographic sector. -* Get ready to scale. -* Create a business case to advance to Beta phase. - -## Third Stage: Implementation - -* Manage expansion to full scale implementation for all products, facilities, and partners. -* Develop a roadmap for long term adoption, that includes ongoing value assessment diff --git a/website/docs/guidance/testing.md b/website/docs/guidance/testing.md index 3fe5ee8f..4a059074 100644 --- a/website/docs/guidance/testing.md +++ b/website/docs/guidance/testing.md @@ -9,5 +9,10 @@ import Disclaimer from '../\_disclaimer.mdx'; An explanation of testing services can be found in the “Testing Services” section of the [UNTP site](https://uncefact.github.io/spec-untp/docs/tools-and-support/TestService). The tools and guidance for their use can be accessed [here](https://github.com/uncefact/tests-untp). -Results from early implementations will enable the CRM project team to create CRM-specific testing services, as needed. +Test implementations assist individual implementers and communities of implementers to test your conformance with UNTP-CRM, prior to broad adoption. +These tools allow early implementers to manually create trial digital credentials, and publish them so they can be accessed by other pilot implementers, such as trading partners, customs authorities, and investors. You can find other planned implementers here, with whom you can test your test implementation. + +* A description of tools for undertaking a test implementation can be found at the [UNTP site](https://uncefact.github.io/tests-untp/). +* The tools and guidance for their use can be accessed [here](https://uncefact.github.io/tests-untp/docs/mock-apps/). + diff --git a/website/docs/register/index.md b/website/docs/register/index.md index 0dda14ee..bb021336 100644 --- a/website/docs/register/index.md +++ b/website/docs/register/index.md @@ -1,6 +1,6 @@ --- sidebar_position: 30 -title: Implementers +title: Register --- This section of the site describes the various types of UNTP-CRM implementers, their roles and function. As you read, consider which role your organization would play as a UNTP-CRM implementer. diff --git a/website/docs/resources/business-case.md b/website/docs/resources/business-case.md deleted file mode 100644 index 94d1cbac..00000000 --- a/website/docs/resources/business-case.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -sidebar_position: 5 -title: Business Case for Implementers ---- - -import Disclaimer from '../\_disclaimer.mdx'; - - - -## Value Proposition for Early Implementers - -Based on our interactions with potential early implementers, we’ve observed a typical engagement pattern, in which an interested party within an organization reaches out to the project team regarding participation as an implementer, and requires additional information about 1) resources required and 2) value of participation. Armed with this information, they can advocate for participation to other relevant decision makers within their organization, such as their sustainability, IT and supply chain leads. With this in mind, we have developed a value proposition template to assist potential implementers to articulate the benefits of participation and resources required for their organization. As you develop your value proposition, we suggest you map and activate your community, as the value of early implementation will increase when multiple parties can share verified data interoperably. - -## Business Case for Implementers - -The decision to move through the phases of UNTP-CRM implementation will need a positive business case to justify the investment. The purpose of this page is to provide a framework for business case development that can be adapted to the stage of implementation and type of implementer. Early implementers can use the [UNTP cost-benefit models and business case templates](https://uncefact.github.io/spec-untp/docs/business-case/BusinessCaseTemplates) to assist with this process. They should provide feedback to the project team to refine these templates for CRM-specific use cases both at individual and community level. diff --git a/website/docs/resources/community-activation.md b/website/docs/resources/community-activation.md deleted file mode 100644 index 2c12386a..00000000 --- a/website/docs/resources/community-activation.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -sidebar_position: 10 -title: Community Activation ---- - -import Disclaimer from '../\_disclaimer.mdx'; - - - -As you develop your value proposition, we suggest you map and activate your community, as the value of implementation will increase when multiple parties can share verified data interoperably. You can find advice and best practices on the [UNTP community activation page](https://uncefact.github.io/spec-untp/docs/business-case/CommunityActivationProgram). As early implementers progress to adoption, they can provide feedback to the CRM project team to develop and refine CRM-specific community activation guidance and tools. diff --git a/website/docs/resources/index.md b/website/docs/resources/index.md deleted file mode 100644 index af7c7cd7..00000000 --- a/website/docs/resources/index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -sidebar_position: 25 -title: Resources and Templates ---- - -This section of the site provides resources and templates for UNTP-CRM implementers to assist their progress through the phases of implementation to full adoption. diff --git a/website/docs/resources/value-assessment.md b/website/docs/resources/value-assessment.md deleted file mode 100644 index ceac8380..00000000 --- a/website/docs/resources/value-assessment.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -sidebar_position: 20 -title: Value Assessment ---- - -import Disclaimer from '../\_disclaimer.mdx'; - - - -Once a community or individual implements UNTP-CRM and transparency data starts to flow at scale, it will become important to continuously assess the actual value that is realised. Dashboards and scorecards that measure key performance indicators will energise ongoing action and provide valuable feedback at both community and national level. Therefore the AATP defines a minimal set of KPIs that each implementer can easily measure and report to their community - and which communities can report to national entities. - diff --git a/website/docs/specification/DigitalTraceabilityEvent.md b/website/docs/specification/DigitalTraceabilityEvent.md new file mode 100644 index 00000000..9be48a3e --- /dev/null +++ b/website/docs/specification/DigitalTraceabilityEvent.md @@ -0,0 +1,47 @@ +--- +sidebar_position: 7 +title: Traceability Events +--- + +import Disclaimer from '../\_disclaimer.mdx'; + + + +## Digital Traceability Events + +The CRMTP digital traceability events are all implemented as profiles of the [UNTP Digital Traceability Event (DTE)](https://uncefact.github.io/spec-untp/docs/specification/DigitalTraceabilityEvents). An CRMTP DTE profile is no different in structure to a UNTP DTE but has specific constraints regarding the identifier schemes and industry vocabularies. Implementers should familiarise with the UNTP DTE before implementing any of the CRMTP traceability event profiles. + +The table lists each CRMTP traceability event type and version as well as it's UNTP version dependency. + +| Name | Current Version |Status| Release Date | UNTP dependency | +| --- | ---- | ------ | --- | --- | +| Bulk mixing event| | Draft| 20-11-2024 |UNTP DTE v0.5.0| +| Smelting event| | Draft| 20-11-2024 |UNTP DTE v0.5.0| +| Refining event | | Draft| 20-11-2024 |UNTP DTE v0.5.0| + +### Logical Model + +All CRMTP traceability events use the [UNTP Digital Traceability Event](https://uncefact.github.io/spec-untp/docs/specification/DigitalTraceabilityEvent) v 0.5.0 logical model without change. AATP only applies specific vocabulary and rules. + +### Technical Artefacts + +Implementers must use the [UNTP DTE Technical Artefacts](https://test.uncefact.org/vocabulary/untp/dte/0/about). v0.5.0 + +## Bulk Miximg Event + +The CRMTP bulk mixing event represents the blending of multiple sourced raw materials into one mixed consignment. It uses the `aggregation` event type with input as a list of identified raw products. + +### Profile Rules + +* list of rules + + +### Working Sample + +sample + +## Smelting Event + +smelting event represents the transformation of raw ore into concentrated product - transformation event.. + + diff --git a/website/docs/specification/index.md b/website/docs/specification/index.md index c8872787..c5718cef 100644 --- a/website/docs/specification/index.md +++ b/website/docs/specification/index.md @@ -1,5 +1,5 @@ --- -sidebar_position: 15 +sidebar_position: 20 title: Technical Specification --- diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js index 2916c843..4972e514 100644 --- a/website/docusaurus.config.js +++ b/website/docusaurus.config.js @@ -74,10 +74,10 @@ const config = { items: [ {to: '/docs/about', label: 'About the project', position: 'right'}, {to: '/docs/processes', label: 'About CRMs', position: 'right'}, + {to: '/docs/business-case', label: 'Business Case', position: 'right'}, {to: '/docs/specification', label: 'The specification', position: 'right'}, - {to: '/docs/guidance', label: 'Implementation guidance', position: 'right'}, - {to: '/docs/resources', label: 'Resources & Templates', position: 'right'}, - {to: '/docs/register', label: 'Implementers', position: 'right'}, + {to: '/docs/guidance', label: 'Guidance', position: 'right'}, + {to: '/docs/register', label: 'Register', position: 'right'}, { href: 'https://uncefact.slack.com/archives/C05AV647QKC', position: 'right',