openBIM is the vendor-neutral building information modeling stack. IFC is the ISO standard, IfcOpenShell + BlenderBIM + Speckle are the open tools, BCF coordinates the issues. The model becomes data your AI agents can actually read — and the licence isn't a recurring six-figure ZAR line item. Cost-honest, vendor-portable, ready for AI takeoff.
openBIM (note the lowercase "open" — it's a buildingSMART trademark) is the umbrella term for vendor-neutral building information modeling. The load-bearing standard is IFC (Industry Foundation Classes), registered as ISO 16739. IFC describes what a building is made of: walls, slabs, beams, doors, MEP runs, spaces, storeys, and the geometric and alphanumeric properties that go with them. It's a data model first, a file format second.
Around IFC sits a real ecosystem of open tools. IfcOpenShell reads, writes, and queries IFC programmatically (Python and C++). BlenderBIM is a Blender add-on that turns the world's most popular open-source 3D suite into a credible BIM authoring tool. Speckle federates models across Revit, ArchiCAD, Tekla, and Rhino with a Git-style versioned data layer. BCF (BIM Collaboration Format) handles model-coordination issues across vendors — the JIRA of construction.
The reason this matters now: IFC is structured data, not a drawing. AI agents, quantity-takeoff engines, programme schedulers, cost models, and compliance checkers can all read it directly without scraping PDFs or interpreting CAD lines. The model is the source of truth, and openBIM makes it portable across the supply chain.
QSs measure from 2D PDFs — a 200-page BOQ takes 3-4 weeks manually. Cost estimates live in Excel with version control by filename. Site instructions go out as voice notes; RFIs get lost in chat threads. Building completes, the O&M manuals are PDFs nobody reads, no digital twin survives. The data leaves with the team. openBIM is what makes that pattern fixable.
A working openBIM stack on a project: an authoring tool that exports IFC, a query and processing layer over the IFC, a federation surface that lets disciplines coordinate across formats, and a coordination protocol for issues. Each component has a credible open option.
ISO 16739. The data model. Walls, slabs, beams, MEP, spaces, properties. Versions matter (IFC4 is current, IFC2x3 is the lowest common denominator). Schema published; readers exist for everything.
Open-source Python + C++ library to read, write, query, and convert IFC. AI takeoff engines, automated checks, custom queries. The lever for "treat the model as data".
Blender add-on. Full BIM authoring inside an open 3D suite. IFC-native: opens, edits, and saves IFC without conversion. Real alternative to ArchiCAD / Revit for projects that don't need vendor-specific extensions.
Connects Revit, ArchiCAD, Tekla, Rhino, AutoCAD, IFC. Git-style versioned data layer over geometry. Federates the disciplines without forcing a single authoring tool.
BIM Collaboration Format. Open issue-tracking protocol for clashes, RFIs, and design questions. Camera viewpoint + comment + linked IFC element. Vendor-neutral; works across any BIM tool that respects it.
xeokit, three.js + IFC.js, BIMsurfer. Stream IFC to a browser. No plugin install, no per-seat licence. The site engineer opens the model on their phone.
A canonical "extract quantities from IFC" snippet to make this concrete:
# Quantity takeoff with IfcOpenShell — extract all walls and their volumes import ifcopenshell import ifcopenshell.util.element as util model = ifcopenshell.open("silvercroft.ifc") for wall in model.by_type("IfcWall"): psets = util.get_psets(wall) qto = psets.get("Qto_WallBaseQuantities", {}) volume = qto.get("NetVolume") storey = util.get_container(wall) print(f"{wall.Name} {storey.Name} {volume}m³")
The cost case is real (no recurring vendor lock-in), but the structural advantage is that the model becomes data your AI agents can read directly. No scraping PDFs, no interpreting drawings, no fighting a vendor's API rate limit. model.by_type("IfcWall") is the entire takeoff engine. Everything we want to do downstream — takeoff, programme, cost, compliance, handover — starts from IFC being a queryable data structure.
SmartBIM, Autodesk Construction Cloud, Trimble Connect, and similar proprietary platforms solve real problems — especially for mega-project coordination at scale. The trade-off is recurring per-seat / per-project licensing in foreign currency, vendor-controlled data formats, and an integration story that runs through the vendor's API roadmap. openBIM solves enough of the same problems for most SA projects at a fraction of the cost, with a portable data layer that survives the vendor.
| Concern | SmartBIM & peers | openBIM stack |
|---|---|---|
| Licence cost (10-seat team, 1 year) | USD $30k–$120k+ (R570k–R2.3m at R19/USD) | R0 (infra + integration time only) |
| Data format | Vendor-proprietary; export via vendor API | IFC (ISO 16739); fully readable without the tool |
| Authoring tool lock-in | Tied to vendor's authoring product | Bring any tool that exports IFC (200+) |
| AI agent integration | Through vendor API (rate-limited, billed) | Direct file access via IfcOpenShell |
| Federation across disciplines | Inside the vendor's ecosystem | Speckle, federated IFCs, BCF for issues |
| FX exposure (ZAR billing) | USD pricing, quarterly revaluation risk | None for the tooling layer |
| Survives the contract | Data trapped if subscription lapses | IFC files are yours, readable forever |
| Where they win | Mega-project coordination at scale, vendor-dedicated support, integrated cost+programme platforms | Anything where the licence cost can fund a junior dev or three site instruments instead |
For most SA mid-market construction projects (R50m–R2bn build value, 5–30 seat coordination team), the openBIM stack covers the same operational ground — takeoff, federation, clash coordination, RFIs, handover — while the licence saving funds the on-site sensors and the agent infrastructure that turn the IFC into operational intelligence. Build Smarter. Build Open.
openBIM is the right answer; it isn't the easy answer. The standards are real but complex; the tooling is improving fast but rough in spots; the SA market still leans Revit-and-Excel by default. Knowing where it bites means you can plan around it.
IFC4 is current; IFC2x3 is widely deployed; IFC4.3 adds infrastructure (rail, road, ports). Mixing versions on a project causes silent property loss. Pin a target version in the BIM Execution Plan and convert on intake.
"Revit can export IFC" is true but flatter than the live model. ArchiCAD's IFC export is generally cleaner. Always validate exported IFC against your acceptance checks before downstream use.
You usually want both the 3D geometry and the property sets. Some workflows extract one and not the other. Check that quantities (Qto_*) and property sets (Pset_*) are present, not just walls drawn in 3D.
For greenfield small/mid projects, BlenderBIM is genuinely usable. For large projects with structural-engineering plugins, MEP routing tools, or specific consultant workflows tied to Revit, the migration cost is real. Pick the battle.
Most SA architectural and structural consultants use Revit or ArchiCAD; some use Allplan or Bentley. Asking for an IFC export is in their existing workflow — getting a clean IFC takes one upfront conversation per discipline. Don't assume; specify.
An openBIM project without a written BIM Execution Plan (BEP) drifts within weeks. The BEP names the IFC version, the federation tool, the BCF cadence, the LOD per phase, and the handover spec. Skip it and you're back to PDFs by month 4.
South African construction has the right shape for openBIM adoption: most consultants already use BIM-capable tools, the cost case is sharp because of FX-denominated licences, the regulatory load (NHBRC, OHSA, SANS, B-BBEE procurement) is heavy and structured, and the contractor ecosystem is varied enough that no single proprietary platform dominates. The pattern fits.
FX-cost lever. SmartBIM-class platforms bill in USD. A 10-seat team at $120/seat/month (USD) runs ~R273k/year at R19/USD — before FX revaluation. The same money funds a junior BIM coordinator local hire and the IFC viewer infrastructure. ZAR-denominated cost stack vs USD-denominated. That's the lever.
Regulatory automation. NHBRC enrolment + technical inspections, OHSA Construction Regulations 2014 (CR), SANS 10400 building regs, Section 21A construction VAT, Section 25 procurement preferential points — SA's regulatory load is structured and queryable. An IFC model with property sets aligned to these requirements lets compliance be checked automatically. Property exists, fire rating present, structural calc reference present — queries, not paperwork.
BIM Execution in the JBCC and NEC contracts. The Joint Building Contracts Committee (JBCC) and NEC4 (used by larger SA contractors and SOEs) both increasingly contemplate BIM deliverables. JBCC Edition 6.2 includes provisions for digital deliverables; NEC4 Option Y(UK)1 is BIM-aware. SA government infrastructure contracts under DPSA and NDPW are starting to mandate IFC handover for major projects.
The contractor ecosystem. WBHO, Group Five, Stefanutti Stocks, Aveng — tier-1 contractors run heterogeneous tooling stacks per project. SmartBIM-style single-vendor lock-in actively conflicts with how SA tier-1s actually deliver projects. openBIM lets the contractor coordinate without forcing a vendor on every consultant.
The flagship SA case for openBIM-as-AI-substrate is the work with Gridline Properties and Grant Kneale — a developer building openBUILD AI as the open smart-building platform. AI takeoff from IFC, 4D programme tied to the model, material tracking, quality capture linked to IFC GUIDs, safety intelligence from site photos, automated SA compliance checking. Silvercroft is the pilot. The full pitch is at dev.2nth.ai/preview/gridlineprop/construction-ai.
openBIM is the data substrate for every other Construction skill. It also connects outward into Data (the model is queryable structured data), Tech (the agents that read it), and Design (the architectural authoring tools that produce it).
openBIM has a small number of authoritative sources. buildingSMART is the standards body, IfcOpenShell + BlenderBIM are the workhorse open tools, Speckle is the modern federation layer, and the academic literature on IFC-driven AI takeoff is rich and accessible.