openBIM Grows a Backbone: Porto's Hackathon, Zurich's Governance, ISO's Compatibility Rules
Porto's openBIM hackathon, Zurich's governance push, and ISO's new IFC compatibility policy — three signals that turn openBIM into infrastructure.
The week openBIM stopped being a slogan and started behaving like an actual standard was — in retrospect — pretty unceremonious. Forty-seven people in Porto built nine working prototypes in fifty hours. A roomful of domain leaders argued governance in Zurich. ISO/TC 59/SC 13 quietly published a compatibility policy nobody outside the standards-committee bubble noticed. Three things, one direction.
←TODAY: buildingSMART met in Zurich on 4–5 February 2026 to set governance toward 2030; the Porto hackathon shipped 9 working IFC tools in 50 hours; ISO codified compatibility rules for IFC.
→3012: A Zurich where the project file you committed to storage in 2026 still opens — and still validates — in whatever software our great-great-grandchildren actually use.
Fulcrum: A standard becomes load-bearing when its rules for changing are written down before its market dominance is contested.
Porto: working code, not slides
The first buildingSMART openBIM Hackathon, judged by Helga Tauscher (HTW Berlin), David Delgado Vendrell (buildingSMART Spain), Mário Coelho (CCG/ZGDV) and Daniel Changas (Esri), produced exactly the artifact this format usually doesn’t: running prototypes. The winning team, BCF Time Machine — Greg Jackson, Louis Trümpler, Phuong Nguyen, Dennis Shelden, Geert Hesselink — built a viewer that lets you navigate historical IFC data alongside its BCF resolution trail. Short sentence; large implication. It treats the IFC file as a versioned data source, not a snapshot. Anyone who has lost a coordination argument to “but in the previous version…” knows why that matters.
The broader pattern was IDS (Information Delivery Specification) being used as a workflow driver, not a checklist — defining requirements, validating IFC, structuring exchanges. Several teams closed the loop with BCF feedback, a couple with AI-assisted issue resolution. 87% of participants said the event improved their openBIM understanding. The real test is how many of those prototypes graduate into commercial tools.
Zurich and ISO: the grown-up paperwork
On 4–5 February 2026 the Domain Leadership Conference closed with formal resolutions to the buildingSMART Board around three uncomfortably-adult problems: cross-domain duplication, governance toward 2030, and how to keep IFC 4.3 boring enough that software vendors will trust their roadmaps to it. The Digital Product Passport (DPP) surfaced as the next big collaboration zone — regulatory in origin but technically interesting enough that the room treated it as an innovation surface, not a compliance burden.
Then the ISO move. ISO/TC 59/SC 13 published a Compatibility Policy for ISO 16739-1 — the standard most of us know as IFC. For the first time there is a written, shared definition of what counts as a breaking change, how deprecation must be handled, how extensions get assessed, and how revisions are evaluated before approval. buildingSMART contributed as a liaison. The policy does a thing standards rarely do early in their life: it codifies the rules for changing the rules.
Atelier: On a small-practice stack — Archicad to Speckle to Bonsai, IFC round-tripping through every joint — this trio of moves tells you what to do next week. Pin your project’s IFC schema in the project handbook (IFC4X3 if your structural engineer is current, IFC2x3 if your client’s facility manager is not), and treat the Wettbewerb-stage tool choice as a 25-year decision rather than a render-engine preference. Tell the Bauleitung that BCF tickets are not optional anymore; they’re how the next iteration finds yours.
Hack: This Hack teaches you to check which IFC schema your project file is locked to — the single most important question if you want it still opening in twenty years. The medium is ifcopenshell, three lines of Python, zero excuses. Run this before you commit a project file to long-term storage; if the schema is not on the bSI-supported list, you have just found your next migration task.
import ifcopenshell
f = ifcopenshell.open("project.ifc")
print(f.schema) # "IFC4", "IFC4X3", "IFC2X3"
print(len(f.by_type("IfcWall")), "walls in", f.schema)
The buildings that aged badly in my generation were not the ugly ones — they were the ones nobody could repair because the proprietary format went dark and no 25-year-old could open the file. The ISO compatibility policy is, in plain terms, a vaccine against that scenario for the open part of the stack. Combined with Zurich’s governance push and Porto’s prototype output, you can now make a defensible 25-year bet on IFC in a way that was honestly nervy three years ago. Pick your tool stack this quarter knowing that.
Two caveats, because nothing is free. First, governance resolutions are paperwork; the real test is whether the bSI Domains actually stop duplicating each other by autumn 2026. Second, the hackathon’s 87% education number depends on vendors integrating those prototypes into commercial tools. History suggests roughly half will. Watch which half — and pressure your software vendors accordingly.
Sources & Further Reading
SOURCE · ↗