Platform · Product twin infrastructure

Passports are the output. The product twin is the infrastructure.

Norruva is the runtime that turns fragmented product, supplier and lifecycle data into a governed product twin. It validates every claim against regulation and evidence, then compiles the Digital Product Passport views each actor is allowed to see.

Start now Contact sales

Fragmented inputs in, compiled passport views out: one governed twin underneath.

The runtime

One pipeline, from fragmented data to a governed passport. Every stage is canonical-model-first, event-driven, evidence-backed and audit-ready, not a form wired to a QR page.

  1. 01

    Ingest & evidence

    Connectors, files, OCR/AI extraction with provenance and confidence.

  2. 02

    Semantic normalization

    Units, materials, AAS & GS1 terms mapped to one ontology.

  3. 03

    Product twin graph

    The canonical graph of identity, composition, supply chain and lifecycle.

  4. 04

    Regulation runtime

    Rule packs model what each product must prove, per sector and jurisdiction.

  5. 05

    Claim & validation

    Evidence-backed claims, checked for sufficiency and publication-readiness.

  6. 06

    Passport compiler

    Actor-specific DPP views generated from approved claims.

  7. 07

    Exchange layer

    AAS/AASX, GS1 Digital Link, EPCIS, JSON-LD, registry, wallet, data spaces.

  8. 08

    Event & audit memory

    Who changed what, under which rule version, audit replay by design.

Why it matters

Most DPP tools are shallow. Compliance isn't. The difference between a disclosure that survives an audit and one that doesn't is what sits underneath it.

The shallow DPP

product form › database › QR page

  • No product hierarchy or composition
  • Fields with no evidence or provenance
  • No access control or actor-specific views
  • No versioning, lifecycle or audit replay

The Norruva runtime

data › governed twin › claims › views

  • A canonical graph of identity, composition and supply chain
  • Evidence-backed claims with provenance and confidence
  • Policy-controlled, actor-specific passport views
  • Versioned lifecycle with full audit replay

“A passport without a governed product twin underneath is just a webpage with compliance risk.”

Most digital twins model how a product works. Norruva models what a product must prove.

The product twin graph

The canonical model of product reality. Not a record. A graph of identity, composition, supply chain, evidence and lifecycle state, at whatever granularity a regulation demands.

Identity & granularity

  1. Product Familyfamily
  2. Product Modelmodel
  3. SKUsku
  4. Batch / Lotbatch
  5. Serialized Itemitem

Every node carries

  • Component, material, substanceComposition for SoC, recycled content, dismantling.
  • Supplier & FacilityWho supplied it, where it was made.
  • Evidence & ClaimsDefensible data points, each with its source.
  • Lifecycle eventsRepair, recycling, ownership, regulatory change.

Illustrative. Object names follow the Norruva canonical model.

Evidence-backed claims

Store claims, not fields. A DPP is generated from approved claims, never raw fields. Each claim carries its evidence, source, confidence and validity, so every published statement is defensible.

  1. Extracted
  2. Pending review
  3. Approved
  4. Published
  5. Expired / Revoked

Claim

Recycled content: 34%

Approved
Confidence
High
Valid until
2027-06-30
Evidence · with its source
supplier_declaration.pdf · p.3
lab_report_2026.pdf · tbl.2

Illustrative claim, fictional sample values.

Regulation-as-runtime

Rules are data, not code. Regulation packs model what a product must prove, per sector, per jurisdiction, with effective dates, so requirements change without rewriting the platform.

Mode 01

Readiness

Ingest a portfolio, extract evidence, check DPP readiness and surface the gaps and supplier actions.

Gap report and supplier actions

Mode 02

Publication

Select the rule pack, validate approved claims, compile actor views, assign GS1 Digital Link, publish.

Published passport views

Mode 03

Runtime

Ingest lifecycle events, detect regulation changes, recalculate state, republish, record the trail.

Living state and audit replay

The rule model: RegulationPack · Requirement · EvidenceRecipe · AccessRule · PublicationRule · EffectiveDate · SectorPack · Jurisdiction

The passport compiler

One twin. The views each actor is allowed to see. DPPs are views, not the system of record. The compiler generates each from approved claims, with its own data access, evidence visibility and publication rules.

Consumer

Sees: care, origin, recyclability

Authority

Sees: full evidence & compliance state

Customs

Sees: identity, origin, classification

Recycler

Sees: materials, substances, dismantling

Repairer

Sees: parts, documentation, repair steps

Supplier

Sees: the scope they contributed

Interoperability & exchange

AAS-compatible, not AAS-dependent. The twin exports through whatever rail the reader speaks. The Asset Administration Shell is one of them, a structured exchange format Norruva ingests and emits, mapped to the canonical twin.

AAS / AASX
Shell + submodels, ingested and exported.
GS1 Digital Link
Resolves the product to its views.
EPCIS
Supply-chain and lifecycle events.
JSON-LD / RDF
Linked-data serialization.
EU DPP Registry
Registry submission packages.
EUDI / EUBW Wallet
Planned: credential exchange with EUDI and business wallets.
Data spaces
Sovereign, policy-governed exchange.
REST / GraphQL
Direct API + webhooks.

AAS-valid is not DPP-ready

A structurally valid AASX can still lack evidence, required fields, access control, actor views and audit trail. Norruva bridges the gap: ingest the shell, then check what compliance actually needs.

POST /twins/importIllustrative

// Illustrative: ingest an AASX package
{
  "format": "aasx",
  "file": "file_9f3a21"
}

// 200 OK
{
  "twin_id": "twin_batt_7F3A",
  "aas_valid": true,
  "dpp_ready": false,
  "missing_evidence": ["carbon_footprint"],
  "views_available": ["consumer", "recycler"]
}

Data spaces

Sovereign exchange, not a public scrape. Partners consume the twin through connectors governed by usage policies negotiated between them. The data owner stays in control, following Gaia-X and IDSA principles.

Norruva connectorEDC-compatible · you
Partner connectorCatena-X · participant

Built around: Data sovereignty · Catena-X · Manufacturing-X / Factory-X

Build it in the Showroom

Model the twin before you go live. In the Showroom you walk the twin on sample data: a simulated AASX import, the evidence gaps, and the views each actor sees, before you activate your Workspace.

Open the Showroom

Build the twin. The passports follow.

Walk the twin in the Showroom, or talk to our team about a product-twin rollout.

Start now Contact sales