The last lesson mentioned buildingSMART briefly, the organisation behind IFC, and touched on its origin as a twelve-company consortium back in 1994. This lesson goes further. buildingSMART's name comes up constantly in construction, in job titles, in software marketing, in conversations about standards, but few people outside the BIM world could actually explain what the organisation does, or why an entire industry follows its standards without being legally required to.
buildingSMART is a not-for-profit, member-based organisation, not a government body and not a software company. It has no authority to fine anyone or enforce anything by law. Its own staff numbers are small, well under a hundred people, which is a modest size for an organisation whose standards now shape workflows across a global industry.
That smallness is not accidental. buildingSMART's own membership documentation states plainly that it is reliant on its members to fund and run its work, projects are co-developed with the industry itself, not handed down independently. The organisation's actual reach comes from its membership base: companies representing owners, architects, engineers, contractors, software vendors, and academic institutions, spread across national chapters worldwide.
Beyond the international body itself, buildingSMART operates through national chapters, buildingSMART UK & Ireland, buildingSMART Deutschland, buildingSMART USA, and many others. As of today, there are 40 national chapters spanning Europe, Asia, North and South America, and Africa, a number that has grown steadily as more countries establish their own chapter. These chapters are not simply local franchises. buildingSMART's own documentation describes them as organisations whose purpose is to "promote and drive forward the active use of open data standards" within their own country, and to identify the specific standards or compliance needs relevant to that market.
This structure explains something worth connecting back to the last lesson. Government adoption of open standards varies significantly from country to country, and that unevenness is not incidental. Each chapter is specifically tasked with pushing adoption forward in its own territory, at its own pace, shaped by its own government relationships and industry maturity. A chapter's not-for-profit status is not just a technicality either. buildingSMART states this directly: that status is "crucial to recognition by governments of the independence of a chapter from any dominating commercial influence," a guarantee that no single software vendor or company is steering the standard for its own benefit.
It is worth being precise about where the money flows, since it explains a lot about who has influence over the standards you use every day. Member organisations pay annual dues directly to buildingSMART, ranging from roughly €8,000 for a small standard membership up to €100,000 for the highest strategic tier. National chapters pay their own fees to the international body too, up to €20,000 a year for a full chapter. None of this money flows back to members as payment. What paying members receive instead is influence: voting rights over how standards like IFC and IDS actually develop, membership in multiple national chapters, certification benefits, and visibility, since being listed as a member or as certified software functions as public proof of commitment to open standards, in an industry where tenders increasingly check for exactly that.
The membership list at the top tiers reads like a map of the entire BIM software industry. Strategic members, the highest and most expensive tier, include ARUP, Siemens, Oracle, and Nemetschek Group, the company that owns ArchiCAD, Allplan, Vectorworks, Solibri, and Bluebeam. Multinational members include Autodesk, Bentley Systems, Trimble, Graphisoft, Dassault Systèmes, and WSP, one of the largest engineering consultancies in the world.
This is not a coincidence. Every major authoring tool in common use, Revit, ArchiCAD, Allplan, Tekla, traces back to a company paying to sit inside buildingSMART's governance structure and vote on how the standard evolves. The companies building the software people use to create IFC files are, in large part, the same companies funding and shaping what IFC actually is.
buildingSMART's core output is IFC, covered in the last lesson, but IFC is only one part of a wider standards family. BCF, short for BIM Collaboration Format, is a format for tracking coordination issues, like clashes, between different software tools. IDS, the Information Delivery Specification, defines what information a model actually needs to contain for a given project. bSDD, the buildingSMART Data Dictionary, standardises the terminology and property names used across all of this, so that "fire rating" means the same thing regardless of which software or country a project sits in. Each of these gets covered properly later in this series. For now, it is enough to know they exist and that buildingSMART maintains all of them as one connected family of standards, not separate, unrelated products.
Since buildingSMART has no regulatory power, it is worth asking honestly why software vendors and firms bother complying with its standards at all, beyond simply paying to join.
Part of the answer is a formal Software Certification Program, separate from general membership. Vendors pay to have their software's IFC import and export tested against buildingSMART's official criteria, €1,500 per tool per IFC version for import, €2,500 for export. This is not a token exercise. Revit received IFC2x3 certification in 2013. Vectorworks has been certified for IFC4 export. This matters because certified software gets listed publicly, and that list gets used directly in real procurement. One industry source puts it plainly: the certified software list is "quite often referenced in tenders to avoid usage of unknown tools," specifically to reduce the risk of a project being unable to collaborate properly across different software. A newer mechanism reinforces this further. buildingSMART's IFC Validation Service now automatically generates public "scorecards" for software tools based on real files uploaded by actual users, not vendor self-reporting, giving buyers an independent, continuously updated view of how well a tool really performs.
Put simply, buildingSMART's standards get followed not because they are mandatory, but because avoiding them creates a real, practical risk: a tool or firm that can't demonstrate compliance becomes a harder sell in an industry where interoperability increasingly gets written directly into contracts and tender requirements. And the firms with the most influence over what "compliance" actually means are, quite directly, the ones paying the most to have a vote in the room.
Comments use a free GitHub account — takes under a minute to create, and keeps discussions spam-free and permanently archived.