Before this is a product story, it is a distributed-systems story — and every small office that has ever fought a merge conflict over a shared model already knows the frontier this touches. When Marc Shapiro and colleagues at INRIA formalised conflict-free replicated data types (CRDTs) around 2011, they answered a deceptively narrow question: how do several people edit one document at once, offline and online, without a central referee, and still converge on one truth? That maths is why two of us can type into the same browser tab and not clobber each other. A building model is the far harder case — not a stream of characters but geometry, issue threads and decisions that all have to agree.

Signal. Graphisoft will use the AIA Conference on Architecture & Design in San Diego on 11–12 June to preview the next phase of its Design Intelligence Strategy: a new open collaboration layer — a Nemetschek Group-level initiative to keep models, documents, issues and decisions synchronised across teams — plus a built-in Archicad↔Autodesk Forma connection. It is designed around five interchange formats — IFC, BCF, PDF, DWG and RVT — with early access later this year. Sylwester Pawluk, VP of product management for collaboration, called it “an intelligent multidisciplinary collaboration environment” bringing “architects, engineers, builders, owners, and operators into a common source of truth.” A separate browser-based AI tool for massing and performance is slated for October.

System. The interesting word is native. Chief product officer Márton Kiss framed the Forma link as “open collaboration and customer choice” — and the honest translation, for a practice, is: your Tragwerksplaner can stay in Revit, your massing can live in Forma, and Archicad stops pretending it’s the only room. Nemetschek — the parent that ad-hoc-news reports is placing a $2.4 billion bet on US expansion — is stitching feasibility-to-lifecycle onto one cloud, with a coordinated October update anchored by Archicad, BIMx, BIMcloud, MEP Designer and DDScad. That is exactly what a Generalplaner mandate needs — and exactly where a studio quietly hands over its coordination habits.

←TODAY: In 2026 a 14-person office still emails a ZIP of the IFC and hopes the round-trip survived. →3012: By the Zurich-3012 horizon the model is a live, versioned commons no single vendor hosts. Fulcrum: A “common source of truth” is only worth trusting if you can prove, on your own desk, what the sync dropped.

Street. Think of a matchday at Letzigrund: eleven players, one pitch, one referee — the whole thing works because everyone reads the same lines on the same grass. Spain did not lift the 2023 title by each footballer keeping a private copy of the pitch. Trade coordination is the same problem: the second the structural, MEP and architectural models each hold a private truth, someone loses a week in the Ausführungsplanung. So the question this announcement forces is not “is the tooling good” but who owns the model, and how do we verify the handover before we trust it.

Atelier: The offices that get hurt are not the ones that adopt late — they are the ones that adopt a different tool every project and never write down how the round-trip actually behaves, so the knowledge walks out with the next Praktikant. Monday move: before you route a single live project through any new collaboration layer, run one deliberate export-import cycle on a real model and diff the element counts by IFC class — make the tool prove it, don’t take the demo’s word.

Hack: Count what survives the round-trip. Point IfcOpenShell at the file you sent and the file that came back, and let the numbers tell you what the sync ate — walls that became proxies, spaces that vanished. Three lines catch a week of grief.

import ifcopenshell
from collections import Counter
m = ifcopenshell.open("after_roundtrip.ifc")
print(Counter(e.is_a() for e in m.by_type("IfcProduct")))
# diff this Counter against the same run on your pre-export file

Run it on both files, subtract, and any non-zero delta is a conversation you want to have before the Bauleitung, not after.

The trade-off, stated plainly: the smoother the native RVT/Forma exchange gets, the more of your coordination discipline is quietly hosted by whichever vendor keeps the truth — convenience and dependence arrive on the same wire, and only your own verification habit tells them apart.

PAZ Takeaway: The seam this announcement lights up — the Grasshopper↔Archicad round-trip and the parts the current connection still leaves missing — is exactly what the PAZ Grasshopper↔Archicad Library and PAZ’s personalised online solutions are built to fill for a specific office: a documented, versioned bridge you own and maintain, not a black box you rent. The value there is not another plugin; it is a pipeline your studio can read.

Move. Pick one live model, run the three-line count on a round-trip, write the result into your BEP, and decide on evidence — not on a San Diego keynote — whether that layer earns a place in how your office owns its model.

Sources & Further Reading

• Primary: AEC Magazine — Graphisoft to preview collaboration layer and Archicad–Forma connection
• Reinforcing: Graphisoft Insights — product news roadmap signal