Start with the uncomfortable framing, because the vendors will not offer it. openBIM is not a feature you switch on. It is a governance choice about who holds the keys to a building’s data over its whole life — and, like most governance choices, it is easiest to make well before the entry contract is signed and nearly impossible to reverse after.

←TODAY: IFC4.3 Add2 shipped in 2023, stretching the open schema from buildings into rail, roads and bridges. →3012: The models still readable in the Zurich-3012 archive are the ones nobody needed a live licence to open. Fulcrum: A format is only open if reading it never depends on paying the party that wrote it.

What it is: openBIM is a workflow built on vendor-neutral standards, stewarded by buildingSMART International, which calls itself — without irony — the “Home of openBIM.” On buildingSMART’s own openBIM page four standards plus one free service do the load-bearing work. IFC (Industry Foundation Classes) carries the geometry and semantics of the asset. BCF (BIM Collaboration Format) routes a clash detected in one program to an answer given in another, without a screenshot in an email. IDS (Information Delivery Specification) writes information requirements a machine can check. bSDD (the buildingSMART Data Dictionary) gives every discipline the same words for the same things. And the free, online Validation Service checks IFC files against that grammar. The claim is modest and enormous at once: the data of a building belongs to the building, not to the seat that happened to draw it.

Here is the control mechanism to watch. The label “Open BIM” has been absorbed into marketing decks. A workflow that exports a proprietary file and re-imports it through one vendor’s cloud is sold as open; it is not. The minimum honest test is whether the process itself is legible — whether you can read the inputs, transform them into whatever outputs you need, and audit the transformation without buying an extra plugin to do it. openBIM meets that bar at the file layer. Full openness — the code behind the exchange laid bare — remains, for most commercial BIM software, an unmet promise.

Why it works: openBIM works because it separates the record from the reader. Proprietary round-trips couple the two: the model you can open is the model your current licence can open. ALLPLAN’s Nigel Rees names the failure bluntly — the round-trip is where information goes to die: a released section dropped, a load case lost, a member that quietly forgot its material. IFC refuses that coupling. It is a text-serialisable schema — STEP-based, and since IFC2x3 in 2006 aligned to the ISO/PAS 16739 registration — that any conforming tool can parse, which means the analysis you run does not depend on the authoring seat that made the geometry.

The engineering payoff compresses to two words: software-version independence. IDS is what turns that independence from a hope into a contract. Instead of trusting a received model and discovering the gaps after they fail, you write the requirements — every wall carries a fire rating, every structural member declares its material — as a machine-checkable specification, and the model is validated before it enters your analysis. buildingSMART runs its free online Validation Service on exactly that pattern. For a load-bearing element, that shift is not convenience. It is provenance: a record that survives every upgrade cycle across the asset’s life.

Origins: The promise has a birthday. In June 1996 the first Industry Foundation Classes, IFC 1.0, shipped as a vendor-neutral data model for the building. IFC2x3, in 2006, hardened the schema and aligned it to ISO/PAS 16739, and it became the first version most of the industry actually exchanged. IFC4 modernised the geometry and semantics. IFC4.3 Add2, in 2023, finally pushed the model out of the building and into infrastructure — rail, roads, bridges, waterways. The politics were baked in from the start: proprietary formats had fragmented AEC into locked rooms, and open formats were the argument for the exit door. Governments now write openBIM into procurement mandates; the Nemetschek Group signed it into an OPEN BIM Charter — a supplier declaring, in effect, that it will compete on tools rather than on lock-in.

The reference projects are coordination stories, not silhouettes. buildingSMART curates the Panama Canal Fourth Bridge, where structural, civil and mechanical models from different authoring tools federated through IFC into one coordinated whole. PAZ’s own concept archive frames the honest small case too — the New School in Holbrook, Massachusetts, where an ALLTO workflow let structural planning proceed from an architectural model without re-drawing it by hand. The building is ordinary. The workflow is the point.

In practice — Atelier: A Swiss studio reaches for openBIM at exactly one moment of maximum risk: the handoff between offices that do not, and should not have to, run the same software. The trade-off is real and worth stating plainly — IFC is verbose, occasionally clumsy, and it will humble anyone who opens the schema; you pay in export discipline for what you gain in provenance. The way to stop paying that cost twice is to make the exchange checkable rather than trusted. Monday move: write one IDS rule for your most safety-critical property set — SIA fire ratings on IfcWall is the obvious first — and run every incoming and outgoing IFC through buildingSMART’s free Validation Service before it leaves or enters the office. One rule, enforced, converts a coordination argument into a failing test. And when you draft the vendor contract, write the exit clause before the entry clause: the price of leaving is the only number that tells you how open the tool really is.

Hack: Turn the fire-rating requirement into a gate that runs itself. The library is IfcOpenShell, the open core of the Native IFC / OSArch movement; the pattern is buildingSMART’s Validation Service in five lines. Point it at a handover file, and any wall missing its Pset_WallCommon.FireRating stops the build instead of reaching the engineer.

import ifcopenshell, ifcopenshell.util.element as el
model = ifcopenshell.open("handover.ifc")
gate = lambda w: el.get_psets(w).get("Pset_WallCommon", {}).get("FireRating")
missing = [w.GlobalId for w in model.by_type("IfcWall") if not gate(w)]
raise SystemExit(missing or "every wall declares its FireRating")

Wire that SystemExit into CI and the requirement checks itself — a bad model never becomes someone else’s problem.

Move: The next argument for openBIM will not be about file formats. It will be about time and standing. IFC4.3 has carried the schema into infrastructure, IDS is turning information requirements into computable contracts, and Native IFC tools are making the open file the thing you author in, not the thing you export to. Follow that line and openBIM stops being a translation layer between rival vendors and becomes the long-term memory of the built environment — the record still readable when the seat that drew it, and the company that sold it, are both gone. The deliverable was never interoperability for one quarter. It was accessibility for the whole life of the asset. Audit your own exports before you trust anyone else’s, and write the exit clause first.

Sources & Further Reading

• Primary: buildingSMART International — What is openBIM?