A digital twin is the complete internal record of an individual physical item, everything you know about it and everything that has happened to it. A Digital Product Passport is a regulated, partial view of that same record, published to people outside your business.<\/p>\n
One record, two jobs. Get that relationship the right way round and most of the difficulty in a passport programme disappears.<\/p>\n
The term arrived from aerospace and manufacturing, where it means a live simulation of a physical asset. That is not what it means for a product.<\/p>\n
For a product, a digital twin is an item-level record with a history. Not the model, not the SKU: the specific unit, with its own identifier, accumulating events for as long as it exists.<\/p>\n
A whisky cask is the clearest example we work with. The twin holds its fill cycles, its warehouse location, every movement it has made and every intervention along the way. Nobody regulates that record. It exists because the owner needs it to run the asset, settle disputes about provenance and prove what is in the cask to a buyer.<\/p>\n
The shape is the useful part. A static specification sheet is not a twin. An event log against a persistent identifier is.<\/p>\n
A Digital Product Passport is a defined set of fields about a product, held in a standard format and reachable from the product itself by scanning a code or tapping a tag. The obligation comes from the Ecodesign for Sustainable Products Regulation and arrives category by category, with batteries, textiles and electronics among the earliest.<\/p>\n
It is narrower than a twin in scope and wider in audience. A twin can hold anything you find useful. A passport holds what the regulation requires, in the format the regulation specifies, for anyone who asks.<\/p>\n
| <\/th>\n | Digital twin<\/th>\n | Product passport<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|
| Owns the scope<\/td>\n | you<\/td>\n | the regulator<\/td>\n<\/tr>\n |
| Audience<\/td>\n | internal, plus chosen partners<\/td>\n | anyone with the item<\/td>\n<\/tr>\n |
| Contents<\/td>\n | everything known about the item<\/td>\n | a defined subset<\/td>\n<\/tr>\n |
| Shape<\/td>\n | event log over the item’s life<\/td>\n | structured, standardised fields<\/td>\n<\/tr>\n |
| Changes when<\/td>\n | anything happens to the item<\/td>\n | the rules change, or the data behind a field does<\/td>\n<\/tr>\n |
| Failure mode<\/td>\n | you cannot answer a question<\/td>\n | non-compliance<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Read that table the right way and the conclusion is straightforward. The passport is a view. Views are cheap when the underlying record is good, and impossible when it is not.<\/p>\n Tiered access: four audiences, one record<\/h2>\nThe regulation does not expect everyone to see the same passport, and this is the part most explainers skip.<\/p>\n Consumers<\/strong> get the plain version. What it is made of, how to care for it, how to repair it, what to do with it at end of life, whether it is genuine. Short, readable, no technical vocabulary.<\/p>\n Recyclers and waste processors<\/strong> get composition and disassembly. Which fractions are present, where the fixings are, which components must be removed before shredding, which substances need handling. They are working at speed on a sorting line, so this view is about machine readability far more than presentation.<\/p>\n Market surveillance authorities<\/strong> get the full record, including conformity documentation, the responsible economic operator and the history of changes. The history matters: they are checking whether a claim held at the time the product was placed on the market, not just whether it is stated today.<\/p>\n Repairers and second-hand sellers<\/strong> need something different again. Parts availability, service history, software support windows, and whether this individual item has an outstanding recall or has been reported stolen.<\/p>\n Four audiences, four views, one record underneath. If you have built the twin, each of these is a filter and a format. If you have built only the consumer page, each one is a new project.<\/p>\n The common approach is passport-first: read the regulation, list the required fields, build something that outputs them. It gets you compliant and it leaves you stuck.<\/p>\n Three things tend to go wrong.<\/p>\n A passport is a snapshot, a twin is a log.<\/strong> Passport-first designs store the current value of each field. Then a surveillance authority asks what the value was eighteen months ago, or a customer asks whether their specific unit was in the affected batch, and there is nowhere to look.<\/p>\n A passport is at batch level, value is at item level.<\/strong> Most passport implementations identify the model or the batch, because that is the minimum the rules require. Every commercially interesting use of the data needs the individual item: ownership, warranty, resale, theft, repair history, refill counts. Retrofitting item identity onto a batch-level system means reissuing the tags.<\/p>\n A passport has one audience in the build, and four in reality.<\/strong> A consumer-facing page hard-codes assumptions about presentation. Then the recycler wants a machine readable feed and the whole thing has to be taken apart.<\/p>\n Build the twin first and the order reverses. The regulation becomes a mapping exercise: these fields of ours, in that format, to that audience, under those access rules. When the delegated act for your category changes, you change a mapping rather than a system.<\/p>\n You do not need to build everything before you start. You need three decisions made in the right order.<\/p>\n Do those three and the passport is a publishing problem. Skip them and it is a data problem, which is a much longer and more expensive kind of problem to have.<\/p>\n One question, on one product line.<\/p>\n For a single unit you shipped last year, can you list what has happened to it since, with dates and sources?<\/strong><\/p>\n If yes, you have a digital twin, whatever you call it internally, and the passport is largely a formatting job. If no, that is the work, and it is worth starting before your category’s deadline rather than after it.<\/p>\n Veribli builds item-level records on tagging technology that has been tracking physical items through circular supply chains for nearly thirty years, including over 900 million refillable containers. The passport is one view onto that record. It is usually not the most valuable one.<\/p>\n To talk through what your category requires and what your data can currently support, call us on 01482 455 855<\/strong>.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":" A digital twin is the complete internal record of an individual physical item, everything you know about it and everything that has happened to it. A Digital Product Passport is a regulated, partial view of that same record, published to people outside your business. One record, two jobs. Get that relationship the right way round… Read More »From digital twin to product passport: one record, two jobs<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":343,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorised"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t |