IFC 4.3 in Practice: Property Sets, MVDs, and openBIM Compliance
IFC 4.3 is the first IFC release to genuinely cover infrastructure alongside buildings, giving organisations a unifying openBIM schema for rail, road, bridges, ports, and tunnels as well as vertical assets. Getting it right in practice means mapping native authoring parameters to standard Pset_ property sets, choosing the correct Model View Definition for the exchange purpose, referencing the buildingSMART Data Dictionary for controlled vocabulary, and validating every export for schema and content compliance. Treating IFC as a first-class, disciplined deliverable rather than a side-export is what makes information genuinely portable across the asset lifecycle.
Why IFC 4.3 Matters Now
IFC 4.3 is the first IFC release that genuinely covers infrastructure: rail, road, bridges, ports, tunnels. For organisations that have to deliver across building and infrastructure portfolios, it is the unifying schema. ISO ratification has accelerated adoption among national mandates, and the buildingSMART certification programme is now meaningfully testing exporters and importers against it.
Property Sets: Native vs IFC
Native authoring tool parameters (Revit shared parameters, ArchiCAD properties, Tekla attributes) do not automatically become IFC property sets. You need an explicit mapping. Decide early whether to use the standard Pset_ definitions (recommended for openBIM exchange) or custom property sets (acceptable for internal workflows). Standard psets travel; custom psets often do not.
Model View Definitions
MVDs constrain the IFC schema to a defined subset for a defined purpose. Reference View is for coordination and visualisation. Design Transfer View attempts geometry round-tripping. Choose deliberately: exporting Design Transfer View when the recipient only needs Reference View bloats files and complicates validation. Most coordination workflows are well served by Reference View plus a documented set of property sets.
buildingSMART Data Dictionary
bSDD provides a controlled vocabulary for properties, classifications, and values across languages and standards. Mapping your project properties to bSDD references future-proofs the data: when downstream consumers (FM systems, asset registers, regulators) ask for a specific classification, you already have the link. Treat bSDD as the canonical reference, not an optional extra.
Validation Workflow
An IFC export is not done when the file writes. Validate with the buildingSMART Validation Service for schema compliance, then with Solibri or BIMcollab Zoom for content compliance against the BEP's information requirements. We run validation as a CI step on every published model: any failure blocks the CDE state transition. Manual validation does not scale and does not happen consistently.
Common Pitfalls
Recurring failure modes: missing IfcSite or IfcBuilding spatial container; geometry exported as IfcBuildingElementProxy because the native object type was not mapped; coordinate reference system not declared (critical for infrastructure georeferencing); units inconsistent across disciplines; psets exported but property values null. A one-page IFC delivery checklist, run before every issue, eliminates 80% of these.
openBIM as a Capability, Not a Format
True openBIM means consumers of your IFC can act on it: query, validate, transform, visualise, federate, hand to FM. That is a capability earned through disciplined authoring, mapping, and validation, not a checkbox in the export dialog. Teams that invest in IFC as a first-class deliverable, not a side-export, find their information genuinely portable across the asset lifecycle.
Frequently asked questions
Why does IFC 4.3 matter for infrastructure and building projects now?
IFC 4.3 is the first IFC release that genuinely covers infrastructure such as rail, road, bridges, ports, and tunnels, making it the unifying schema for organisations that deliver across both building and infrastructure portfolios. ISO ratification has accelerated adoption among national mandates, and the buildingSMART certification programme is now meaningfully testing exporters and importers against the schema.
Should I use standard or custom IFC property sets?
Native authoring tool parameters, such as Revit shared parameters, ArchiCAD properties, or Tekla attributes, do not automatically become IFC property sets and need an explicit mapping. Standard Pset_ definitions are recommended for openBIM exchange because they travel reliably between platforms, while custom property sets are acceptable for internal workflows but often do not survive cross-platform handover.
Which Model View Definition should I choose for IFC exports?
Model View Definitions constrain the IFC schema to a defined subset for a defined purpose. Reference View suits coordination and visualisation, while Design Transfer View attempts full geometry round-tripping. The choice should be deliberate: exporting Design Transfer View when the recipient only needs Reference View bloats files and complicates validation, and most coordination workflows are well served by Reference View plus a documented set of property sets.
What role does the buildingSMART Data Dictionary play in IFC delivery?
The buildingSMART Data Dictionary, or bSDD, provides a controlled vocabulary for properties, classifications, and values across languages and standards. Mapping project properties to bSDD references future-proofs the data, so that when downstream consumers such as FM systems, asset registers, or regulators ask for a specific classification, the link is already established. It should be treated as the canonical reference rather than an optional extra.
What are the most common mistakes in IFC file delivery?
Recurring failure modes include a missing IfcSite or IfcBuilding spatial container, geometry exported as IfcBuildingElementProxy because the native object type was not mapped, an undeclared coordinate reference system, inconsistent units across disciplines, and property sets exported with null values. Running a one-page IFC delivery checklist before every issue eliminates the large majority of these problems, and validating every export with the buildingSMART Validation Service plus a tool like Solibri or BIMcollab Zoom catches what the checklist misses.
Related services
Related case studies
Need help implementing this in your projects?
We build production-grade systems, not theoretical frameworks. Let's discuss your specific challenges.