How the Digital Product Passport Connects to BIM: From Manufacturer Data to the Model
The DPP is not a compliance PDF with a QR code on it. It's a legal requirement that a product's data speak the same language as your BIM model. Here's the actual mechanism that makes that possible.
Everyone talks about the Digital Product Passport as a compliance document, something a manufacturer generates to prove a product meets EU requirements. That's true, but it misses the more interesting part. Under the revised Construction Products Regulation, that data is legally required to stay interoperable with BIM, which means the passport is not meant to live in a separate compliance folder at all. It's meant to reach the model.
What the Digital Product Passport actually is
The Digital Product Passport, DPP, is a structured, machine readable record attached to a product, covering things like materials, sustainability performance, and compliance status. For construction products specifically, it isn't a standalone EU scheme. It's delivered through the revised CPR, Regulation (EU) 2024/3110, which we covered in our CPR explainer, and it shares its underlying legal framework and shared registry with the broader ESPR, which we covered separately. What makes the construction version distinct is one specific requirement most summaries skip past.
Why CPR requires DPP to work with BIM
The text of the revised CPR is explicit that a construction product's digital passport has to be developed without compromising interoperability with Building Information Modelling. That's not a nice-to-have mentioned in a footnote, it's written into the regulation that shapes how manufacturers are supposed to build this data in the first place. The reasoning is straightforward once you say it out loud: construction products already live inside BIM models for most of their working life, from specification through to as-built handover, so a compliance record that can't be read by the same systems is a record most of the industry will end up re-typing by hand.
The technical bridge: ISO 23386, ISO 23387, and bSDD
Two ISO standards, developed by ISO/TC 59/SC 13 together with CEN/TC 442, define the actual mechanism behind that legal requirement. EN ISO 23386 sets the methodology for describing and maintaining properties inside shared, interconnected data dictionaries, giving every organisation involved a common governance process instead of everyone inventing their own property names. EN ISO 23387 builds on that by defining data templates, structured digital representations of construction objects and the properties that describe them, linked back to those dictionary entries.
If that sounds familiar, it should. It's the same underlying approach behind bSDD, the buildingSMART Data Dictionary we explained previously, which is itself built on ISO 12006-3 and already hosts over 300 dictionaries in active use. bSDD gives a property like fire rating or global warming potential a stable, language independent identifier. A manufacturer can build a Digital Product Passport template on those same bSDD referenced properties, and a BIM model can reference the identical properties through IFC or an IDS check. The passport and the model aren't translating between two different vocabularies, they're pointing at one shared definition.
From manufacturer to model: what this looks like in practice
In practice, the connection has two layers. The digital layer is the one described above: a product's data template, its EPD figures, and its DoPC under the revised CPR can all reference the same defined properties that a BIM object also uses, so importing one into a model doesn't mean retyping the other. The physical layer is what actually links a real product on a real site back to that digital record, typically a QR code, an NFC chip, or an RFID tag on the product itself, which some manufacturers are already attaching to BIM objects they publish, alongside a direct link to the product's passport.
Industry sources are consistent on one point worth taking seriously: the data requirements for a construction DPP overlap heavily with what Environmental Product Declarations and BIM product data templates already capture. A manufacturer that has already invested in a well structured BIM object has not started from zero on their DPP, a meaningful share of that work already exists, it just hasn't always been organised around a shared, referenceable dictionary yet.
What's still manual, and what changes
None of this is fully automatic across the industry today, and it's worth being honest about that rather than describing a pipeline that doesn't exist yet everywhere. Most manufacturers have not yet rebuilt their product data around bSDD referenced properties, which means a lot of the actual linking happening right now is still someone copying figures out of an EPD PDF into a BIM object by hand. What's changing is the pressure pushing that to stop being normal: the DoPC, the Declaration of Performance and Conformity that replaced the old DoP, has been required to be machine readable since CPR became applicable on 8 January 2026, and the shared DPP registry has been operational since 19 July 2026. Neither of those dates makes the manual work disappear overnight, but both make structured, referenceable product data the thing regulation is steering toward, not an optional extra.
Why this matters for BIM managers
If you manage BIM data on real projects, the practical takeaway isn't to wait for a finished pipeline before paying attention. It's to start noticing which of your manufacturers already publish BIM objects with bSDD referenced properties or direct DPP links, and which still hand you a PDF and a QR code that goes nowhere useful. That difference is going to matter more with each CPR milestone that passes, and the vendors ahead of it now are a reasonable signal of who will make your model, and your compliance file, less work to maintain later.
Want to understand the standards actually doing this work, not just the regulation naming them? Our buildingSMART Professional Certification Programme covers IFC and bSDD data dictionaries directly in Module 4. See the full catalogue on our courses page.
Frequently asked questions
The Digital Product Passport, DPP, is a structured, machine readable record of a product's data, covering things like materials, sustainability performance, and compliance. For construction products it is delivered through the revised Construction Products Regulation, CPR, which requires this data to be interoperable with Building Information Modelling standards, not just readable by a compliance officer.
Mostly no. Industry sources note that DPP data requirements align closely with what Environmental Product Declarations and BIM product data templates already capture, so a manufacturer with an existing, well structured BIM object has already done a large share of the work a DPP needs.
Two ISO standards define the mechanism: EN ISO 23386 sets the methodology for describing and maintaining properties in shared data dictionaries, and EN ISO 23387 builds structured data templates on top of that. buildingSMART's bSDD is the working, publicly usable implementation of that same approach.
bSDD gives each product property a stable, language independent identifier. A manufacturer can build a Digital Product Passport template on bSDD referenced properties, and a BIM model can reference the exact same properties, so the DPP and the model point to one shared definition instead of two separate, disconnected datasets.
Some manufacturers already publish BIM objects that include links to a product's sustainability or compliance data, and physical tags such as QR codes, NFC chips, or RFID connect the physical product back to its digital record. This is not yet a single standardised format across the industry, so availability still varies by manufacturer.
Today, a lot of the real work is still someone copying data between an EPD document and a BIM object by hand, because most manufacturers have not yet built their DPP data on bSDD referenced properties. That is expected to shift as CPR's requirement for a machine readable Declaration of Performance and Conformity, in force since 8 January 2026, and the DPP registry, operational since 19 July 2026, push structured, referenceable product data from the exception toward the default.
Learn DPP Properly,
Not Just the Headlines
Why it's worth it:
-
The full regulatory picture, not just the deadline. ESPR and CPR explained together, with the real timeline.
-
What's actually inside a DPP. Real data fields and how governance works once it's a system of record.
-
Where this is going next. A bonus module on AI in DPP.
-
A certificate on completion, plus team licenses for whole organizations.
