From DPP Readiness to Defensible Supplier Evidence: A Worked Manufacturer Example
From DPP Readiness to Defensible Supplier Evidence: A Worked Manufacturer Example
From DPP Readiness to Defensible Supplier Evidence
One manufacturer, one product family, three tools, and the moment the data stops being 'somewhere' and starts being owned.
Aurelia Lighting GmbH is fictional. It is not a tieback customer, and the figures, suppliers and documents below are illustrative. Nothing here is a regulatory determination, a mandatory field list or advice on what any specific product must publish. The point is the method, not the numbers.
This example follows one manufacturer through the three practical tools in the Templates pillar, in the order they are meant to be used. Each part shows what the team put in, what the tool gave back, and what changed in how they thought about their own data. You can open each tool and repeat the exercise on your own product as you go.
The Scenario
Aurelia has been asked by two large customers when its passport data will be available, and its commercial team has started answering sustainability questions in tenders. Nobody inside the company believes the answers are wrong. Nobody can say where they came from either.
The team’s own framing at the start is the one most manufacturers begin with: we have most of the data, we just need to get it into a passport. That framing is what the exercise tests.
Where the data actually lives
Product identifiers, supplier ids, purchase records, item master attributes
Attributes copied in from elsewhere are indistinguishable from attributes it owns.
Bill of materials, drawings, component specifications for the AL-400
Authoritative for design intent, but not connected to anything downstream.
Selected material and sustainability figures collected for tenders
No stated method, no version history, no named owner.
Declarations, certificates and test documents from component suppliers
Held as attachments; nobody records whether any of it was accepted.
Everything that did not fit anywhere else
Inconsistent naming, unclear currency, ownership by memory.
Read as a list, this looks like reasonable coverage. That is precisely the trap: coverage describes what exists, not what can be relied on. The first tool is designed to separate the two.
Part 1: DPP Readiness Assessment
The team scores ten dimensions on the six level maturity scale, using the levels honestly rather than aspirationally. Four dimensions are gating: a weakness in any one of them holds the whole programme back regardless of strength elsewhere.
The assessment applies the Product Data Maturity Model (TBF-024) and the readiness dimensions of TBF-011. The levels below are the team’s inputs. Everything after them is computed by the same model the tool uses.
Information can be found by people who know where to look. Nothing is yet measurable or repeatable. The programme is held at level 1 by Authoritative data sources and Governance and ownership, however strong the other dimensions are.
| Dimension | Level | What the team recorded |
|---|---|---|
| Regulatory applicabilitygating | 2 · Quality | The team knows ESPR exists and that a product specific measure would drive the field list. Nothing is written down per product family. |
| Product identificationgating | 4 · Integration | Luminaires carry stable, externally resolvable identifiers, allocated by a controlled process. The strongest dimension. |
| Product data availability | 3 · Governance | Most expected content exists somewhere; the condition of it has been assessed informally. |
| Authoritative data sourcesgating | 1 · Collection | Values exist in several systems at once and nothing arbitrates between the copies. |
| Supplier data | 1 · Collection | Supplier information arrives by email, on request, in whatever format arrives. |
| Evidence and verification | 1 · Collection | Evidence is filed rather than accepted. No record of who reviewed it or when. |
| Standards and interoperability | 2 · Quality | Identifiers follow a standard; data structures do not. No machine readable exchange. |
| Systems and integration | 2 · Quality | ERP and engineering files are reconciled by hand each time. |
| Governance and ownershipgating | 1 · Collection | No named owner for passport relevant attributes. Definitions live in people. |
| Operational readiness | 2 · Quality | No process for updates, corrections or re-issue after a change. |
- Establish authoritative sources for the AL-400 attributes, one attribute at a time.
- Resolve supplier held evidence gaps for the components that carry claims.
- Assign ownership so definitions and changes have a named person behind them.
- Only then consider integration and automation between the systems.
The shape is common and worth reading carefully. Aurelia is strong exactly where manufacturers are usually strong, identification and raw availability, and weak exactly where passport work is actually decided: which copy of a value is authoritative, what stands behind it, and who owns it.
Readiness is not an average. Aurelia’s average sits in the Emerging band, but the programme is constrained at level 1 by the two gating dimensions it scored lowest on. Investing in integration now would connect systems that still disagree with each other, and propagate the disagreement faster. The sequence the tool produces is deliberate: designate authority, close evidence gaps, assign ownership, and only then automate.
Score your own ten dimensions. The banding, the constraint and the priority order are computed the same way as above.
Part 2: Passport Data Origin Worksheet
The readiness assessment said authoritative sources were the binding constraint. The worksheet is where that abstraction becomes a list of named items. For each one the team records four things: the information, its origin today, the authoritative source for it, and the evidence position behind it.
This applies the Passport Data Origin Model (TBF-042), with readiness states from TBF-003. The statuses below are derived by the worksheet’s own rules, not asserted by the team: an item is a gap when the authoritative source or the evidence position is not established, and partial when those are settled but something practical, an owner, fitness, verification, an open action, is not.
Seven representative items from the AL-400 follow. A real worksheet for this family would run to several dozen rows.
| Information | Origin today | Authoritative source | Evidence position | Status |
|---|---|---|---|---|
| Product identifier for the AL-400 and its variantsProduct identity and reference data | Enterprise resource planningItem master, identifier allocated at variant level | Product data lead, allocation registerManufacturer's designated product master | Internal control, none required (decided)Allocation register with change history | Ready |
| Manufacturing location for the finished luminaireManufacturing and production data | Enterprise resource planningProduction plant recorded against the works order | Operations, Rheine assembly siteProduction site | Batch and quality control recordsWorks order and batch records | Ready |
| Product mass, assembled luminaire with packagingProduct identity and reference data | Product lifecycle managementCalculated from the BOM, not weighed | Engineering, AL-400 design ownerSpecification owner | Calculation, study and methodologyBOM roll up; method not written down | Partial |
| Aluminium alloy designation for the housing extrusionComposition and materials | Supplier portals and submissionsSupplier material data sheet held as an email attachment | Extrusion supplier, material specificationThe supplying organisation | Supplier declarationMaterial data sheet, currency unverified | Partial |
| LED module technical specification as suppliedSupplier-provided data | Supplier portals and submissionsModule datasheet, revision held in the engineering folder | LED module supplier, product specificationThe supplying organisation | Supplier declarationSupplier datasheet, revision D | Partial |
| Driver conformity and test evidence for the electronic control gearCompliance and conformity information | Supplier portals and submissionsDeclaration of conformity and test report from the driver supplier | Driver supplier, as the economic operator placing the componentThe economic operator carrying the legal duty | Declaration of conformity or technical documentationDeclaration of conformity plus referenced test report | Partial |
| Recycled content share of the aluminium housingSustainability and environmental information | Enterprise resource planningA percentage keyed into the item master for a tender in 2024 | Not establishedNot yet decided | Not yet decidedOriginal supplier statement not located | Gap |
2 Ready · 4 Partial · 1 Gap
The discovery
A recycled content percentage sits in the item master and has been quoted in tender responses. It was keyed in from a supplier statement that nobody can now locate.
The ERP holds that figure. The ERP is not authoritative for it. It is a consuming system for a value whose authoritative basis is supplier evidence that was never obtained in a controlled way. The worksheet records it as a gap, and the gap is the useful output: it moves the figure out of the item master, where it looked settled, and into the evidence register, where it can be closed.
Holding a value and being authoritative for it are different claims, and systems of record blur them constantly. Once Aurelia separates the two, three quarters of its rows turn out to be partial rather than ready, not because the data is wrong, but because currency, method or ownership was never recorded. That is not a setback. It is the first accurate picture the team has had.
Trace your own items. Everything stays in your browser, and the worksheet exports to CSV for your programme records.
Part 3: Supplier Evidence Register
Four of the seven traced items depend on information Aurelia does not hold itself. Those become register entries, where the question changes from “what is the value” to “what stands behind the value, who issued it, has it been accepted, and is it still current”.
This applies the DPP Evidence Lifecycle (TBF-034) for evidence kinds and states, and the Supplier DPP Readiness Model (TBF-032) for supplier segmentation. Statuses are again derived by the register, not chosen.
- Scope
- AL-400, all variants, driver type D-48
- Supplier
- Driver supplier, Netherlands · Tier A, critical
- Evidence expected
- Technical documentation · Declaration of conformity naming the applied standards, with the referenced test report
- Evidence state
- Accepted
- Issuer and standing
- Driver supplier, regulatory affairs · Authoritative source
- Reference
- DOC-D48-2026-02 and TR-D48-118
- Validity
- Current · Valid for the current driver revision; re-check on revision change
- Owner
- Quality, Quality manager
- Next action
- Re-verify on driver revision or standard update.
Accepted after review against the applied standards, not on receipt.
- Scope
- AL-400 housing extrusion, profile P-220
- Supplier
- Extrusion supplier, Germany · Tier B, important
- Evidence expected
- Supplier documentation · Current material data sheet with an issue date and the alloy designation
- Evidence state
- Received
- Issuer and standing
- Extrusion supplier, technical sales · Supplier assertion
- Reference
- MDS-P220 (undated copy)
- Validity
- Not established · No issue date on the copy held; currency cannot be established
- Owner
- Engineering, Materials engineer
- Next action
- Request a dated, current data sheet and record the issue date.
Received is not accepted. The document exists; its currency does not yet support a claim.
- Scope
- AL-400 housing extrusion, profile P-220
- Supplier
- Extrusion supplier, Germany · Tier B, important
- Evidence expected
- Declaration · Supplier declaration stating the share, the calculation method and the reporting period
- Evidence state
- Received
- Issuer and standing
- Extrusion supplier, sustainability contact · Supplier assertion
- Reference
- Email statement, 2026-05-04
- Validity
- Not established · Reporting period not stated, so the figure cannot be tied to any period
- Owner
- Sustainability, Sustainability lead
- Next action
- Ask for the method and the reporting period before the figure is used again.
This is the ERP figure traced back to its origin. Issuer is known; the position is still not defensible.
- Scope
- AL-400, module M-92
- Supplier
- LED module supplier, Asia, via EU distributor · Beyond the direct supplier
- Evidence expected
- Not yet decided
- Evidence state
- Not requested
- Issuer and standing
- Not established · Not yet established
- Reference
- None recorded
- Validity
- Not established
- Owner
- Procurement, Category buyer
- Next action
- Decide what evidence is expected, then route the request through the EU distributor.
Information originates beyond the direct supplier, which lengthens every request.
- Scope
- AL-400 outer carton and inserts
- Supplier
- Packaging supplier, Germany · Tier C, standard
- Evidence expected
- Supplier documentation · Specification stating the fibre composition of carton and inserts
- Evidence state
- Accepted
- Issuer and standing
- Packaging supplier, technical · Supplier assertion
- Reference
- PKG-SPEC-2026-01
- Validity
- No expiry applies (decided) · Specification stands until the packaging is changed
- Owner
- Procurement, Category buyer
- Next action
- Re-verify at the next packaging change.
A supplier assertion, accepted knowingly for a low criticality item.
2 Ready · 2 Under review · 1 Gap
What the register makes visible
- Received is not accepted. The alloy data sheet and the recycled content statement both exist. Neither supports a published claim yet, for different reasons: one has no issue date, the other no reporting period. A folder full of documents hides this distinction; the register cannot.
- Standing matters as much as content. The driver conformity evidence is accepted because it was reviewed against the standards it applies, and because the issuer is the party legally responsible for the component. The packaging specification is accepted knowingly as a supplier assertion, because the criticality does not warrant more. Both are defensible. They are defensible for different reasons, and the register records which.
- Distance lengthens every request. The LED substance declaration has to travel through an EU distributor to a supplier beyond the direct relationship. Nothing is wrong with the supplier; the route is simply longer, and planning that assumes a direct ask will be late.
- Ownership converts a problem into a queue. Every open row has a named function and person, so follow up is scheduled work rather than an act of memory.
The recycled content figure travels the full length of the exercise: strong looking in the ERP, ungoverned in the worksheet, and finally an owned, dated, actionable gap in the register. Aurelia now knows it cannot publish that claim yet, and knows exactly what has to arrive before it can. Discovering that here costs an email. Discovering it after publication costs a correction.
Track your own supplier-held requirements, their evidence state, validity and next action. Exports to CSV or TSV.
What Changed
Note what is not on that list. Aurelia has not published a passport, bought software, or completed its data. It has ten defensible statements about its own product family and a short list of things it knows are missing, which is a materially stronger position than believing everything is fine.
The Sequence, and Why It Holds
Establishes what is actually constraining the programme, so effort is not spent on the wrong dimension.
Turns the constraint into named items with an origin, an authoritative source and an evidence position.
Takes the supplier-held items and drives each to an accepted, current, owned evidence position.
A product family whose passport-relevant claims are traceable to an authoritative source, supported by evidence of known standing, and owned by named people with a dated action list for what is still open.
The order is not decorative. Skipping the assessment produces a worksheet that traces the wrong items. Skipping the worksheet produces a register full of requests nobody can justify. Skipping the register produces a passport whose claims cannot be defended when someone asks.
How To Repeat This
- Pick one product family, not your whole catalogue. Scope is what makes the exercise finishable.
- Run the readiness assessment with the people who actually maintain the data, and score honestly.
- Take the weakest gating dimension into the data origin worksheet and trace ten to twenty real items.
- Move every supplier-held item into the supplier evidence register and record what evidence you expect before you ask for anything.
- Re-score readiness after the first round of gaps closes. The movement, not the absolute level, is the signal.
If you want the underlying method rather than the worked artefacts, the Academy Foundations path teaches the same models in sequence, and the tieback Framework Library holds the canonical definitions the tools apply.
Limitations
- Aurelia Lighting GmbH, its suppliers, documents and figures are fictional and illustrative.
- The scoring, statuses and bands are produced by the same models the Templates use, but the inputs are chosen to be instructive rather than typical of any particular company.
- Nothing here determines which obligations apply to any product, or which fields any passport must carry. Applicability follows the instrument and the product specific measure for your product and market.
- The tools are worksheets. They record positions and actions; they do not verify evidence, contact suppliers or produce a compliance conclusion.
Related Articles
- Supplier Evidence Register
- Passport Data Origin Worksheet
- DPP Readiness Assessment
- What Data Goes in a Digital Product Passport, and Where Does It Come From?
- How Will Digital Product Passports Change Product Compliance?
- Product Data
- Sustainability Data
- What Are the Benefits of a Digital Product Passport?
References
- Regulation (EU) 2024/1781 (Ecodesign for Sustainable Products Regulation), Chapter III on the Digital Product Passport: https://eur-lex.europa.eu/eli/reg/2024/1781/oj
- tieback Knowledge, “How to Build a Trusted Product Data Foundation” (TBF-024, the maturity scale used in Part 1): https://tieback.io/docs/knowledge-base/enterprise-systems-and-data-architecture/how-to-build-a-trusted-product-data-foundation
- tieback Knowledge, “What Data Goes in a Digital Product Passport, and Where Does It Come From?” (TBF-042, the data origin model used in Part 2): https://tieback.io/docs/knowledge-base/digital-product-passports/what-data-goes-in-a-digital-product-passport
- tieback Knowledge, “How to Manage Evidence for Digital Product Passports” (TBF-034, the evidence lifecycle used in Part 3): https://tieback.io/docs/knowledge-base/implementation/how-to-manage-evidence-for-digital-product-passports
- tieback Knowledge, “How to Prepare Suppliers for Digital Product Passports” (TBF-032, supplier segmentation): https://tieback.io/docs/knowledge-base/implementation/how-to-prepare-suppliers-for-digital-product-passports
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.
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.