Mapping of workshop themes to framework components
| Workshop theme | Indicative expert inputs (examples) | Implication identified | Corresponding DDIF framework element(s) |
|---|---|---|---|
| Lifecycle data continuity and traceability gaps | “Data disappears after handover”; “No continuity between construction and demolition data” | Need for continuous, dynamic lifecycle data capture across A–D stages | Digital lifecycle monitoring and updates (Section 4.5); DPP creation logic |
| Interoperability and standards alignment challenges | “Systems don’t talk to each other”; “too many proprietary formats” | Requirement for standardised data templates and open interoperability | Data collection and standardisation (Section 4.2); technological integration (Section 4.3) |
| Unclear stakeholder roles and data ownership | “Who owns the passport data?”; “responsibilities shift across lifecycle stages” | Need to explicitly define stakeholder responsibilities and access rights | Initiation and planning (Section 4.1); reporting and sharing (Section 4.7); governance (Section 4.8) |
| Weak integration of end-of-life feedback into design | “Demolition data is never reused”; “design teams don’t learn from end-of-life” | Need for feedback loops linking end-of-life outcomes to future projects | End-of-life and circularity assessment (Section 4.6); DMB integration |
| Governance, reporting, and regulatory readiness | “Frameworks must support ESG reporting”; “policy alignment is essential” | Necessity for governance, auditing, and compliance mechanisms | Reporting and sharing (Section 4.7); review and governance (Section 4.8) |
| Workshop theme | Indicative expert inputs (examples) | Implication identified | Corresponding |
|---|---|---|---|
| Lifecycle data continuity and traceability gaps | “Data disappears after handover”; “No continuity between construction and demolition data” | Need for continuous, dynamic lifecycle data capture across A–D stages | Digital lifecycle monitoring and updates (Section 4.5); |
| Interoperability and standards alignment challenges | “Systems don’t talk to each other”; “too many proprietary formats” | Requirement for standardised data templates and open interoperability | Data collection and standardisation (Section 4.2); technological integration (Section 4.3) |
| Unclear stakeholder roles and data ownership | “Who owns the passport data?”; “responsibilities shift across lifecycle stages” | Need to explicitly define stakeholder responsibilities and access rights | Initiation and planning (Section 4.1); reporting and sharing (Section 4.7); governance (Section 4.8) |
| Weak integration of end-of-life feedback into design | “Demolition data is never reused”; “design teams don’t learn from end-of-life” | Need for feedback loops linking end-of-life outcomes to future projects | End-of-life and circularity assessment (Section 4.6); |
| Governance, reporting, and regulatory readiness | “Frameworks must support | Necessity for governance, auditing, and compliance mechanisms | Reporting and sharing (Section 4.7); review and governance (Section 4.8) |
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.