Connecting BIM with material data across the building lifecycle
Building information modeling has reshaped how geometry, schedules and asset information are coordinated, yet the materials that actually go into a wall, slab or façade often remain locked in separate PDFs and datasheets. As the built environment faces pressure to cut embodied carbon and recover resources, the conversation is shifting from what a model contains to what the model knows about each product inside it. Embedding structured material data into BIM is moving from a niche interest to a baseline expectation for design teams, manufacturers and asset owners.
For Australian practitioners, the shift is arriving alongside tighter requirements in the National Construction Code, the spread of Green Star and NABERS assessments, and the scale-up of public infrastructure programmes from Sydney to Perth. The XIII International Conference on Building Materials and Components in São Paulo offers a timely venue to compare how different jurisdictions are connecting digital models with the physical resources they describe.
Why material data belongs inside BIM
A BIM model is most useful when it carries information that can be queried and reused. Embedding properties such as density, thermal conductivity, recycled content, expected service life and references to Environmental Product Declarations turns a 3D representation into a structured dataset. Designers can evaluate options against carbon budgets, quantity surveyors can refine cost plans, and facility managers can plan maintenance using the same source of truth. Without this layer, BIM remains largely a geometric exercise that has to be redone every time a new question is asked.
The information is also valuable earlier than the operational stage. During schematic design, knowing the embodied carbon of alternative concrete mixes or steel sections can redirect decisions before they are locked in. Linking these properties to BIM objects allows sustainability analysis, code checking and procurement reviews to run continuously rather than as one-off exercises late in the project.
Standards and data structures that make it possible
Material data often stays out of BIM because it does not fit a single schema. Industry Foundation Classes provide a broad container for properties attached to objects, while the buildingSMART Data Dictionary offers a shared vocabulary for product characteristics. COBie remains a popular handover format, and the buildingSMART Product Data Template gives manufacturers a standard way to publish properties that plug directly into BIM tools. Each addresses a different part of the lifecycle, and most projects use several at once.
The lesson from Australian and European pilots is that no single standard covers everything. Teams that succeed treat the standards as a layered system: IFC for geometry, the Data Dictionary for naming, product templates for specification, and COBie or linked data for handover. The goal is to keep information moving without re-keying it at every stage.
Material passports and embodied carbon
Material passports extend the idea of product data by recording what is installed, where, and how it can be recovered. When connected to BIM, they let a building be queried for its total material stock, its ability to be disassembled, and the carbon stored in its components. This is increasingly relevant for adaptive reuse in Australian inner-city projects in Sydney, Melbourne and Brisbane, where heritage overlays and floor-area constraints push teams toward retention rather than demolition.
Embodied carbon is becoming a regulated metric as well as a voluntary one. The National Construction Code is progressively tightening expectations for commercial buildings, and the Green Building Council of Australia's Green Star tool already rewards measurable reductions. Reliable, model-based material data is what makes these assessments defensible and repeatable.
Australian drivers shaping adoption
Australian projects operate under a layered system of federal, state and market-based requirements. The National Construction Code sets baseline performance expectations, while state agencies in New South Wales, Victoria and Queensland publish their own BIM and information management rules for transport, health and housing work. On top of this, voluntary rating schemes push the agenda further for clients who want to demonstrate sustainability outcomes.
Several local factors are pushing material data integration forward:
- The National Construction Code is moving toward embodied carbon disclosure for commercial buildings.
- State agencies in New South Wales, Victoria and Queensland publish BIM requirements for transport and social housing projects.
- Voluntary schemes such as Green Star, NABERS and the Infrastructure Sustainability rating reward data-rich material specifications.
- Major programmes including Sydney Metro, Melbourne's Suburban Rail Loop and Brisbane's 2032 Olympic venues are raising the bar for information delivery.
- Local climate risks, from bushfire-prone interfaces to cyclone-exposed coastal sites, demand context-specific material properties stored in the model.
Workflows on Australian projects
On a typical mid-rise project, structured material data can start with manufacturer BIM objects for major systems and be enriched through specification tools linked to product data templates. Sustainability consultants pull EPDs into the model to support Green Star submissions, while the cost planner uses the same data to align quantities and rates. At handover, the model is exported through COBie or IFC to feed the asset register used by facilities teams. The data flow is rarely linear, but the principle is to capture information once and reuse it.
Large public projects are pushing the approach further by requiring information delivery specifications that name the material properties, classifications and formats expected at each milestone. Smaller practices can adopt lighter versions, focusing on a handful of critical products such as structural concrete, façade glazing and key mechanical components rather than the full material list.
Interoperability challenges and a practical starting checklist
Even with mature standards, friction remains. Manufacturers publish data in different formats, software vendors interpret IFC slightly differently, and project teams often have to reconcile multiple classification systems such as Uniclass, OmniClass and NATSPEC. Linked data, web services and APIs are helping, but they require investment in data governance that smaller firms may struggle to justify.
A useful starting checklist for teams new to this work:
- Identify the three or four material categories that drive the most carbon or cost on your projects.
- Confirm the information delivery requirements in your client contract and align internal templates.
- Map existing product data sources to a recognised schema such as the buildingSMART product data template.
- Assign clear ownership for updating material data at each project stage.
- Plan a post-handover review of the material data that actually proved useful in operations.
Material data formats commonly paired with BIM:
| Format | Primary use | Strength | Typical stakeholder |
|---|---|---|---|
| IFC | Geometry and property exchange | Open schema with wide software support | BIM managers, designers |
| COBie | Asset handover | Structured spreadsheet format with a long track record | Facility managers |
| EPD | Environmental declaration | Verified, third-party reviewed LCA data | Sustainability consultants |
| Material passport | Lifecycle and circularity | Captures recovery and reuse potential | Owners, asset managers |
| bSDD / product data template | Shared product vocabulary | Centralised, multilingual definitions | Manufacturers, specifiers |
The next step for any team is to pick one live project and pilot structured material data on a single building system, such as the structural frame or the façade, using the formats already required by the client. The lessons from that small pilot will shape a broader rollout far more effectively than any strategy document, and they will give the team concrete examples to bring to the DBMC conference in São Paulo.