01
Product structure
Configure the industrial product family, reusable product data and passport template within the manufacturer’s secure tenant.
Anonymised industrial pilot
Digital Product Passport for Industrial Equipment
How a high-capacity synthetic lifting product was connected to a serialised digital identity, NFC and QR access, controlled evidence, lifecycle events and a public passport.
UK industrial manufacturerLong-life lifting productControlled pilot
Product
Serialised synthetic lifting assembly
Pilot objective
Prove physical-to-digital traceability
Identifier access
NFC tag with printed QR fallback
The challenge
A product with a long operational life and distributed evidence
Industrial lifting products can remain in service for years and pass between manufacturers, asset owners, operators, inspectors and service providers. Their useful information is rarely held in one place.
Shared product specifications, item-level serial data, declarations, technical drawings, inspection records and lifecycle events may sit across documents, enterprise systems and separate organisations.
The pilot therefore tested more than a digital label: it tested whether one physical product could maintain a governed, verifiable identity across its lifecycle.
Physical-to-digital workflow
Six connected stages, one persistent product identity
02
Serialised asset
Create a persistent record for one physical lifting product, separating shared model data from item-specific identity and history.
03
NFC and QR access
Associate one resolver URL with the physical tag and QR fallback so both carriers open the same trusted digital identity.
04
Evidence links
Connect controlled technical documents and immutable document versions to the relevant asset, event or passport version.
05
Lifecycle events
Record authorised events such as manufacture, issue, inspection, repair or retirement without overwriting earlier history.
06
Published passport
Resolve the physical product to a mobile-first public passport containing only information approved for public visibility.
Governance built into the pilot
Controls needed for credible B2B traceability
The pilot architecture separated configuration, tenant operations and public access. That protects customer data while allowing selected product information to travel with the physical asset.
Tenant separation
The manufacturer’s organisations, users, products and records remain within a defined customer data boundary.
Versioned templates
Published template versions remain stable so future configuration changes do not silently alter historical passports.
Frozen published identity
The published passport retains the identity and template version used when it was created.
Granular visibility
Public, customer, supply-chain, auditor and internal information can be treated differently.
Append-only history
Lifecycle corrections are represented transparently instead of deleting or rewriting the original event.
Private evidence storage
Public proof links can be issued securely without exposing the underlying document store.
Physical validation
What the controlled pilot demonstrated
These checks validate the technical workflow. They do not represent a conformity assessment or claim that the product is already subject to a product-specific ESPR DPP obligation.
- A printed QR code opened the correct resolver URL and published passport.
- A rewritable NFC Type 5 sample tag was encoded, read and opened on a smartphone.
- NFC and QR could point to the same logical identifier rather than creating duplicate product identities.
- The public passport rendered across desktop, tablet and mobile layouts.
- Public evidence was accessible while internal evidence remained outside the public view.
- Published passport history remained separated from later template changes.
Practical lessons
What manufacturers should learn from the pilot
Start with data, not the tag
NFC and QR provide access. The hard work is defining authoritative product data, evidence, ownership, validation and update rules.
Separate master and item data
Reusable product-family information should not be copied manually into every serialised asset or allowed to overwrite historical records.
Design visibility deliberately
A public passport should never expose every internal document. Classify data and evidence before publication.
Test one real product end to end
A physical pilot reveals gaps in identifiers, attachment, mobile behaviour, documents and operating responsibility that a slide deck cannot.
Plan a controlled DPP pilot
Turn one real industrial product into a verifiable digital asset
UniQorn Trace™ provides the multi-tenant identity, evidence, access and lifecycle foundation needed to test a practical product-passport workflow.
Case-study note: The manufacturer is intentionally anonymised. This page describes a controlled technical pilot and does not disclose customer documents, identifiers or commercially sensitive product data. It is not legal advice, certification or proof of regulatory conformity.