RBTP · RMI / RMAP

RBTP MVD for RMI/RMAP

Use RBTP minimum verifiable datasets (MVDs) and verifiable credentials to make RMAP due diligence faster, more trusted, and more interoperable across multi-tier mineral supply chains.

Back to RBTP + MVD Task Force →

Purpose

RMAP is a global due-diligence benchmark for mineral supply chains, including 3TG, cobalt, lithium, and other critical materials. Traditional workflows often suffer from fragmented data, repeated submissions, report fatigue, and limited trust across supply-chain tiers.

RBTP can convert selected due-diligence claims into verifiable data points. Downstream customers, auditors, and other authorized reviewers can check a signed credential or linked evidence package without rebuilding the full evidence trail each time.

RMAP Five-Step Framework

  • Step 1: Management systems. Policies, governance roles, traceability, supplier requirements, and grievance channels.
  • Step 2: Risk identification and assessment. CAHRA review, high-risk origins, red flags, and specific risks such as child labor or forced labor.
  • Step 3: Risk response. Management reporting, mitigation plans, improvement pathways, suspension, or disengagement where appropriate.
  • Step 4: Independent assessment. Third-party assessment through RMAP or RMAP+ and related conformance findings.
  • Step 5: Annual reporting. Public disclosure of due-diligence policies, risks, mitigation actions, and assessment outcomes.

RBTP and MVD Design

RBTP builds on UNTP and W3C Verifiable Credentials. It uses open protocols, tamper-evident signatures, and data-owner-controlled sharing. The Sustainability Vocabulary Catalog (SVC) provides shared semantics, while MVDs identify the minimum critical fields needed for verification.

Typical credentials may include digital compliance credentials for RMAP outcomes, digital product passports, facility records, and traceability events.

Mapping RMAP to SVC and MVD Fields

  • Step 1: Policies, traceability, and grievance systems map to fields such as PolicyPublished, TraceabilitySystem, and GrievanceCoverage.
  • Step 2: CAHRA screening, red flags, and human-rights risks map to fields such as CAHRA_Sources, RedFlagsDetected, and ChildOrForcedLaborRisk.
  • Step 3: Mitigation planning maps to fields such as MitigationPlan, ActionsCompleted, and CAPA_Progress.
  • Step 4: Assessment outcomes map to fields such as AssessmentDate, AssessmentBody, Standard, Result, and ValidTo.
  • Step 5: Reporting maps to fields such as AnnualReportPublished, HighRiskSupplyShare, RisksIdentified, and RisksMitigated.

Digital Execution Flow

  1. Define MVD fields against RMAP requirements and SVC terms.
  2. Prepare evidence and identify the owner, source, date, and verification status of each field.
  3. Allow qualified reviewers or assessors to mark findings and verification status.
  4. Issue digital compliance credentials that include key fields, status, and validity conditions.
  5. Update credentials as CAPA actions are closed, reassessments occur, or annual reporting is refreshed.

Data Sharing and Customer Review

  • Downstream due diligence: Suppliers can share credentials that are checked for signature, issuer, and validity.
  • Data-space interoperability: Credentials can support future integration with battery-passport, conflict-mineral, or sector data-space workflows.
  • Finance and procurement: Banks, buyers, and tendering parties can verify selected evidence faster than paper packages.
  • Selective disclosure: Sensitive fields can be controlled while still supporting verification.

Performance Compared with Traditional Workflows

  • Consistency: Standardized fields and semantics reduce format mismatch.
  • Trust: Signatures and timestamps improve confidence in the evidence chain.
  • Efficiency: Credentials reduce repeated document exchange and review cycles.
  • Collaboration: A verifiable data chain supports clearer tier-to-tier communication.
  • Traceability: Evidence can remain linked across facilities, materials, events, and review cycles.

Pilots and Outlook

Parallel RMAP-RBTP pilots point to practical questions around missing-data placeholders, cross-platform recognition, chain-of-custody evidence, and permissioned sharing. Regulatory trends, including supply-chain due diligence and product-passport requirements, are also increasing demand for reusable evidence rather than static reports.

Conclusion

RBTP MVDs can help digitize selected RMAP requirements as reusable, verifiable, and privacy-aware credentials. The next priorities are system integration, assessor training, SVC alignment, data security, and incentives that make responsible mineral data easier to maintain and verify.

Back to RBTP + MVD Task Force →