tieback Knowledge Hub
Vendor-neutral education for Digital Product Passports, enterprise product data, regulations, standards and implementation.
Nothing in this library recommends a vendor, including tieback. Every canonical article is grounded in primary sources, introduces one original framework, and ends in practical guidance. Start with the Knowledge Journey below if the subject is new, choose a learning path if you know where your gap is, or go straight to the glossary to check a term.
The Knowledge Journey
The library is ordered, and the order matters. Each pillar answers a question the previous pillar raises, and depends on the understanding the previous pillar establishes. The Digital Product Passport Knowledge Model sets out that order.
What a passport is, who is responsible for it, what it contains and how it resolves from a physical product. Establishes the vocabulary every later pillar uses.
02RegulationsObligationThe Ecodesign for Sustainable Products Regulation, delegated acts, product scope and timing. Converts a concept into a dated obligation attached to named economic operators.
03Standards & TechnologyMechanismIdentifiers, GS1 Digital Link, data carriers, event standards and the movement of product data between parties. Explains the mechanics that make a regulated claim resolvable.
04Enterprise Systems & Data ArchitectureSourceMaster data, the division of responsibility between PLM, ERP, PIM and MES, governance and the maturity of the underlying data foundation. The pillar most programmes underestimate.
05ImplementationDeliveryPreparation, sequencing, scoping and the operating model that keeps a passport estate accurate after launch. Turns architecture into a plan with owners and dates.
06Industry GuidesContextSector-specific application: textiles, electronics, batteries, construction products and others, where obligations, data availability and supply chain structure differ materially.
What becomes possible when product information is governed, connected and machine readable. This pillar will appear in the navigation when its first canonical article is published.
Read downward to learn the subject. Read upward to diagnose a problem: an implementation failure is usually a data architecture gap, which is usually a standards misunderstanding, which is usually an unclear reading of the obligation.
Learning Paths
Each path is sequenced so that terminology introduced early is assumed later. Counts and first articles are derived from the published library.
Start from the concept itself: what a passport is, who owns it, what it holds and how it is reached from a physical product.
Start with: What is a Digital Product Passport?Start this path7 articlesUnderstand the RegulationsEstablish what applies to your products, from when, and on whose legal authority.
Start with: What is the Ecodesign for Sustainable Products Regulation (ESPR)?
Start this path10 articlesStandards & TechnologyIdentification, carriers, resolution and event data: the mechanics that make a regulated claim resolvable.
Start with: The Digital Product Passport Standards Landscape
Start this path11 articlesEnterprise ArchitectureWhere published information actually comes from, and what must be true of it before publication.
Start with: What is Product Master Data?Start this path8 articlesImplementationPreparing an organisation, sequencing the work and operating a passport estate after launch.
Start with: How Should Organisations Prepare for Digital Product Passports?
Start this pathReaders who sample articles out of order should keep the glossary open, because definitions of record live there rather than being restated in every article.
Browse by Role
Each role links to the path that answers its first question. None are exclusive, and most readers eventually need two of them.
What applies, to which products, from when, and what evidence an authority can request.
Start the Regulations pathWhich system owns which attribute, where the integration layer sits, and where lineage is retained.
Start the Enterprise pathSizing the work honestly: maturity, the gap between a pilot and a capability, and standing cost.
What a passport presents to a customer, what it commits the organisation to, and what it constrains.
Start the introductory pathThe obligations that attach to the manufacturer, and the data that must exist before publication.
Start the introductory pathWhat may be placed on the market, how carriers behave in store and online, and what to require of suppliers.
Start the Standards pathConnecting disclosure obligations to the attributes and evidence that make claims defensible.
Start the Regulations pathFollowing identifiers and events across trading partners, and specifying supplier data.
Start the Standards pathBrowse by Pillar
Counts are derived from the published navigation. Section overviews and glossary entries are not counted.
How the library is organised and where to begin, depending on prior knowledge.
6 articlesDigital Product PassportsDefinition, responsibility, content, resolution mechanics and the benefits claimed for them.
7 articlesRegulationsESPR, delegated acts, product scope and the timeline that turns policy into a dated obligation.
10 articlesStandards & TechnologyIdentification, GS1 Digital Link, carriers, event standards and data movement between partners.
11 articlesEnterprise Systems & Data ArchitectureMaster data, system responsibilities, integration, governance and data foundation maturity.
8 articlesImplementationPreparing an organisation, sequencing the work and operating a passport estate after launch.
1 articleGovernance & AssuranceWho is responsible, who decides, what evidence can be trusted and how the passport stays controlled.
6 articlesIndustry GuidesSector-specific application for textiles, electronics, batteries and other regulated categories.
Framework Library
In this library, a framework is an original conceptual model created to make a subject navigable: a named set of ordered components that explains how something works, what depends on what, and where an organisation currently sits.
Every canonical article introduces exactly one framework, and every framework carries a permanent
identifier in the form TBF-001. The
tieback Framework Library is the authoritative registry
of the full set, with the identifier, the model it names and the article that introduces it. The
selection below links straight to those source articles.
Further frameworks are introduced across the Standards & Technology pillar, including the Product Identity Stack, the Product Identity Hierarchy, the Product Information Delivery Model and the Product Event Lifecycle.
Browse the Framework Library for the complete registry, including every framework identifier and its source article.
Glossary
47 terms, A to ZThe Digital Product Passport GlossaryThe canonical terminology reference for the Knowledge Base. Each entry states what a term means, where the definition comes from and how it differs from the terms it is confused with. Canonical articles link to the glossary rather than restating definitions, so a correction is made once.
Browse the glossary A to ZLatest Canonical Articles
- From DPP Readiness to Defensible Supplier Evidence: A Worked Manufacturer Example
- DPP Governance: Who Owns What?
- DPP Readiness Assessment
- Passport Data Origin Worksheet
- Supplier Evidence Register
- Building an Enterprise Digital Product Passport Architecture
Featured Learning Resources
What a passport is, what it is not, and the four layers that make one work.
PillarRegulationsESPR, delegated acts, scope and timing, read from the Official Journal rather than from secondary summaries.
PillarStandards & TechnologyIdentifiers, carriers, resolution and event data: the mechanics behind a working passport.
PillarEnterprise Systems & Data ArchitectureWhere the information in a passport comes from, and what must be true before it is published.
ReferenceGlossaryDefinitions of record for the terminology used across every pillar, with sources and distinctions.
About tieback Knowledge
tieback Knowledge is a permanent reference library for practitioners who make decisions with legal and financial consequences. It exists so that a reader arriving with any level of prior knowledge can find a defensible answer, and so that the relationship between the pillars is explicit rather than implied by a menu. It avoids marketing language, avoids predicting outcomes that legislation has not fixed, and states clearly when something is not yet determined.
- Vendor neutral. No article recommends a product or platform, including tieback’s. Where a capability is described, it is described as a capability, so the reader can evaluate any implementation of it against the same criteria.
- Primary-source grounded. Regulatory statements are taken from the Official Journal of the European Union, standards statements from ISO, GS1 and equivalent bodies. Every article lists its sources, and secondary commentary is not treated as authority.
- Original educational frameworks. Each canonical article introduces one framework that makes its subject navigable and reusable, rather than restating material available elsewhere.
- Practical implementation guidance. Articles end where the reader has to act: what to do, in what order, and what commonly goes wrong.
- Continuously maintained. Regulation, delegated acts and standards move. Every page carries a last reviewed date and a scheduled review date, and material change triggers revision rather than a new post.
Readers with existing expertise should enter at the pillar that matches their gap rather than starting at pillar one. The Knowledge Model describes dependency, not a required reading order for specialists.
About This Article
tieback Knowledge is a continuously maintained reference library covering Digital Product Passports, product traceability, product compliance and related regulations. Articles are reviewed regularly as legislation, standards and implementation guidance evolve.