How a New BIM Software Company Joins IFC — and Why It Matters
How a New BIM Software Company
Joins IFC — and Why It Matters
The complete insider guide to buildingSMART membership, IFC certification, and the global market access system that separates serious BIM vendors from the noise
By The AEC Intelligence Editorial Team · AI Workflow Blog · Published May 2026 · Last Updated May 2026 · 30 min read
Editorial Note: All membership fees, certification procedures, and programme details in this article are based on buildingSMART International’s publicly available documentation as of May 2026. Fees and procedures change; verify current requirements directly at buildingsmart.org before making business decisions. This article has no commercial relationship with buildingSMART International or any vendor mentioned.
The Situation in One Paragraph
If you are building a BIM software product and want to sell it into government-mandated markets — UK, South Korea, Singapore, EU procurement, US federal agencies, Australia — IFC certification and buildingSMART membership are not optional extras. They are the entry ticket. Without them, your product cannot legally claim IFC compliance, cannot appear on government-approved software lists, and cannot integrate with the rest of the world’s BIM ecosystem. This guide explains exactly what buildingSMART International is, what IFC certification requires technically and legally, what membership costs and gives you, and the complete step-by-step roadmap from founding a BIM startup to achieving certified market entry.
Contents
1 — What Is buildingSMART International and Why Does It Control BIM Market Access?
buildingSMART International (bSI) is the international non-profit organisation that owns, develops, and publishes the open standards on which the global BIM industry runs. It is the body that controls the IFC specification, the BCF (BIM Collaboration Format), the bSDD (buildingSMART Data Dictionary), and the certification programmes that allow software vendors to prove their products work with those standards.
Understanding why this organisation has the power it does requires a short history lesson. In the mid-1990s, major construction technology companies and government bodies recognised that the proprietary file format wars in CAD (every vendor locking clients into their own format) were damaging the industry. In 1994, a consortium of 12 US companies — led by Autodesk — formed the Industry Alliance for Interoperability. By 1997 this had become the International Alliance for Interoperability (IAI), the predecessor of buildingSMART. The goal was to create a vendor-neutral data standard so that a model created in software A could be opened and used meaningfully in software B.
That standard became IFC. And because every major BIM mandate worldwide references IFC as the required open exchange format, buildingSMART — as the owner and steward of IFC — became the de facto gatekeeper to the global BIM market.
buildingSMART’s Organisational Structure
| Layer | Body | Role |
| International | buildingSMART International (bSI) — headquartered in London/Oslo | Owns all standards (IFC, BCF, bSDD). Runs global certification programme. Sets strategic direction. Manages relationship with ISO (IFC is ISO 16739) |
| Regional Chapters | buildingSMART UK, buildingSMART US, buildingSMART Korea, buildingSMART Germany, buildingSMART Australasia, buildingSMART Nordic, etc. (30+ chapters) | Deliver national programmes, training, events. Liaise with local government on BIM policy. First point of contact for new members in that country |
| Technical Rooms | IFC Development Room, BCF Room, bSDD Room, Infrastructure Room, Railway Room, Bridges Room, Tunnels Room | Working groups that develop and maintain the standards. Open to participation by members. Where IFC schema extensions and new features are discussed and developed |
| Certification Body | bSI Certification Programme (managed centrally) | Runs the IFC certification test suite. Awards certification marks. Maintains the certified products register. Enforces compliance with certification requirements |
Why This Matters for a New Vendor
You can write excellent BIM software without being a buildingSMART member. You can implement the IFC schema without certification. But you cannot claim IFC certification without going through bSI’s programme. And in a growing number of government procurement contexts — UK, Korea, Singapore, Netherlands, Australia, Nordic countries — only certified products are considered IFC-compliant for the purposes of contract specification. The market increasingly treats buildingSMART certification as the baseline expectation, not a premium differentiator.
2 — The IFC Standard: What It Is Technically and What Certification Proves
Before you can understand the certification process, you need to understand what IFC actually is — technically, not just as a marketing concept. IFC is simultaneously a data schema, a file format, and a set of rules about how building information must be structured to be interoperable.
IFC in Technical Terms
IFC (Industry Foundation Classes) is an object-oriented data model defined in EXPRESS language (ISO 10303-11) and serialised in one of three exchange formats:
| Format | Extension | Based On | Use Case | Status |
| STEP | .ifc | ISO 10303-21 (STEP Physical File) | File exchange, archiving, procurement deliverables | Primary / required for certification |
| ifcXML | .ifcXML | XML serialisation of IFC schema | Web services, partial model exchange, API integration | Supported but larger file size |
| ifcZIP | .ifcZIP | ZIP-compressed .ifc or .ifcXML | File transfer, storage optimisation | Commonly used |
IFC is also now available as ifcJSON (experimental, for web/API contexts) and as IFC.js (WebAssembly-based browser rendering). These are not yet part of the formal certification test suite as of 2026 but are under active development by buildingSMART.
IFC Versions: Which One to Target
| Version | ISO Status | Certification Available | Primary Use | Notes |
| IFC2x3 | ISO 16739:2005 | Legacy certification (being phased out) | Still dominant in many existing implementations; most installed base | Do not target for new products; support for backward compatibility only |
| IFC4 ADD2 TC1 | ISO 16739-1:2018 | Active certification available | UK, Korea, Singapore, Netherlands mandates; buildings BIM | Primary certification target for building-focused products |
| IFC4.3 | ISO 16739-1:2024 | Active certification — infrastructure focus | Roads, railways, bridges, tunnels, ports; IFC Rail included | Required target for any infrastructure / civil engineering product |
| IFC5 | Under development | Not yet available | Urban scale, digital twin, AI-queryable BIM; expected 2027+ | Monitor development; participate in working groups if targeting next-gen platforms |
What IFC Certification Actually Proves — and What It Doesn’t
|
What certification proves ✓ › Your software exports well-formed IFC files that conform to the IFC schema › Your software imports valid IFC files without data loss on tested entity types › The geometry representations in your IFC export are readable by other certified software › Your declared Model View Definition (MVD) scope is implemented correctly › You are authorised to display the buildingSMART certification mark |
What certification does NOT prove ✗ › That your software supports all IFC entity types (only the declared MVD scope) › That round-trip exchange (export then re-import) produces identical data › That vendor-specific property sets (Psets) are correctly populated › That your software meets any particular LOD (Level of Development) standard › That your software will work seamlessly with all other certified products in practice |
3 — buildingSMART Membership: Tiers, Costs, and What You Actually Get
buildingSMART International membership is the commercial relationship you establish with the organisation. Certification is a separate process (covered in Section 4), but membership unlocks access to the certification programme, the standards development process, the certified products registry, and the chapter network. Here is the complete picture of what membership costs and delivers.
Membership Tiers (buildingSMART International, 2026)
| Tier | Annual Fee (approx.) | Typical Members | Key Benefits | Standards Voting |
| Associate | Free – low fee (varies by chapter) | Individuals, students, small practices exploring BIM | Community access, newsletter, some events; no certification access | No |
| Professional | ~€2,000–5,000/year | Small software companies, consultancies, design practices | Access to certification programme; standards documentation; working group participation; chapter events; listed on member directory | Observer only |
| Vendor Member | ~€5,000–15,000/year | Mid-sized BIM software vendors, technology providers | Full certification access; voting rights in working groups; certified products registry listing; co-marketing; technical support from bSI | Working group voting |
| Strategic Member | ~€20,000–50,000/year | Major vendors (Autodesk, Trimble, Bentley, Nemetschek, Vectorworks), large government agencies | Board-level influence; priority in standards development; dedicated bSI technical liaison; co-branded events; multiple product certifications included | Board-level influence |
| Government Member | Custom (national chapter based) | National government bodies, standards institutes (BSI, AFNOR, DIN, KATS) | Policy input into standards; national mandate alignment; co-development of national BIM requirements | Strategic voting |
Important: Membership Fees Are Layered
The fees above are for bSI international membership. In most cases you also pay a national chapter fee on top of this (buildingSMART UK, buildingSMART Korea, buildingSMART US, etc.). Chapter fees vary from €500 to €5,000/year depending on the chapter and your organisation size. Total annual cost for a typical BIM startup entering the market: €7,000–20,000/year for international + chapter membership at the Vendor Member tier, before certification fees.
What Membership Gives You in Practice
|
▶ Standards Access & Development Full access to IFC schema documentation, EXPRESS files, MVD definitions, and implementation guidance. Participation in Technical Rooms where the next version of IFC is being written. This is where you can advocate for your product’s use cases to be included in the standard. |
▶ Certification Programme Access Only members can apply for IFC certification. The certification fee is separate from membership but membership is a prerequisite. Member status gives you access to the test suite documentation, the testing portal, and technical support during the certification process. |
|
▶ Certified Products Register Once certified, your software appears on buildingSMART’s public certified products database at “validated.buildingsmart.org”. Government procurement officers, BIM managers, and enterprise buyers actively check this register. It is the equivalent of an FDA approval list for BIM software. |
▶ Chapter Network & Market Intelligence Access to national chapter events, working groups, and policy discussions. This is where you learn about upcoming procurement changes, new government BIM requirements, and make the connections with system integrators and resellers who sell into government markets. |
4 — IFC Certification: The Complete Technical Process Step by Step
IFC certification is the technical process by which buildingSMART verifies that your software correctly implements a defined subset of the IFC standard. It is not a one-time award — it is tied to a specific software version, a specific IFC version, and a specific Model View Definition (MVD). When your software gets a major update, you need to re-certify.
The Certification Process: Step-by-Step
|
1
|
Become a buildingSMART Member Certification is only open to members. Join at Vendor Member tier minimum. Complete the online application at buildingsmart.org, pay annual membership fee, sign the member agreement. Processing time: 1–3 weeks. You will receive member credentials and access to the member portal. |
|
2
|
Define Your Certification Scope (Choose Your MVD) An MVD (Model View Definition) is a precisely defined subset of the IFC schema that describes what information must be present for a specific use case. You do not certify against all of IFC — you certify against one or more MVDs that match what your software does. Key MVDs currently available for certification:
|
|
3
|
Submit the Certification Application Through the member portal, submit a certification application specifying: software name and version number, target IFC version, target MVD(s), export capability / import capability / both, and your organisation’s technical contact. Pay the certification fee. Certification fee as of 2026: approximately €1,500–3,500 per MVD per software version (fee varies by member tier — higher tier members pay lower certification fees). The application triggers the creation of a certification run on the bSI testing infrastructure. |
|
4
|
Run the Automated Test Suite You will be given access to the bSI IFC validation service (“IFC Validator” at validate.buildingsmart.org). This tool runs automated tests against IFC files you export from your software. You upload test files; the validator runs hundreds of automated checks and returns a detailed pass/fail report. For import testing, you download reference IFC files from bSI and must demonstrate that your software correctly reads them. The test process is self-service: you run the tests, review the results, fix issues in your software, and re-run until you pass. There is no limit on the number of test runs during the certification period. |
|
5
|
Submit Passing Test Results for Review Once your software passes all required tests in the automated suite, you submit the results package to bSI for review. bSI staff review the submission to verify the test results are genuine and complete. They may request clarification on edge cases or additional evidence of specific capability. This review typically takes 2–4 weeks. |
|
6
|
Receive Certification — Listed on the Certified Products Register Upon successful review, buildingSMART issues the certification for that specific software version and MVD. Your product is added to the publicly searchable certified products register at validate.buildingsmart.org. You receive: (a) a certification certificate document, (b) authorisation to use the buildingSMART certification mark in marketing materials, and (c) the entry on the certified register. Total elapsed time from application to certification: typically 3–6 months for a well-prepared team; up to 12+ months for teams encountering significant IFC implementation issues. |
|
7
|
Maintain Certification — Re-Certify on Major Version Updates Certification is valid for a specific software version. When you release a major update that changes IFC export/import behaviour, you must re-certify. Minor patch releases that do not affect IFC implementation do not typically require re-certification, but you must notify bSI. Annual membership renewal is also required to maintain the certification listing. If you let your membership lapse, your product is removed from the certified register even if the software itself has not changed. |
5 — The IFC Certification Test Suite: What Gets Tested and How
The technical heart of IFC certification is the test suite. Understanding what it tests — and what it does not — is essential for your development team to prepare correctly. Most certification failures come from teams that underestimate the specificity of what the tests check.
What the Automated Validator Tests
| Test Category | What Is Checked | Common Failure Reason |
| Schema conformance | Every IFC entity in the file must be a valid instance of the declared schema; required attributes must be present and correctly typed | Null values in required fields; wrong data type (string instead of enum); invalid entity references |
| WHERE rules | The IFC schema includes EXPRESS WHERE rules that constrain valid values beyond data typing. Every WHERE rule must be satisfied by every entity instance | IfcAxis2Placement3D with non-orthogonal axes; IfcProfileDef with zero-area profiles; IfcMaterial with empty name |
| Geometry validity | All geometry representations must produce valid, non-self-intersecting solids; BREP faces must be correctly oriented; swept solids must have valid profiles and directions | Reversed face normals; open shells (missing faces); degenerate sweep paths; near-zero-thickness walls |
| MVD-specific rules | Each MVD defines additional constraints beyond schema conformance. Reference View requires tessellated geometry (not parametric); Design Transfer View requires parametric representations | Exporting IfcExtrudedAreaSolid for Reference View (requires tessellated IfcFacetedBrep or IfcPolygonalFaceSet); missing IfcRelSpaceBoundary for thermal analysis |
| Object classification | Elements must be correctly typed: walls as IfcWall, doors as IfcDoor, beams as IfcBeam; objects must be contained in appropriate spatial structure (IfcBuilding/IfcBuildingStorey/IfcSpace) | All elements exported as IfcBuildingElementProxy (generic catch-all); elements not placed in spatial structure; wrong predefined type enum values |
| Relationship integrity | Relationships between entities must be bidirectionally consistent; no dangling references; IfcRelContainedInSpatialStructure must reference valid spatial elements | One-way relationships (A references B but B does not list A); stale GUID references from copy/paste errors |
| Units and coordinates | IfcUnitAssignment must correctly declare all units used in the file; coordinate precision and consistency checked | Missing IfcSIUnit declarations; mixing millimetres and metres without unit conversion; incorrect IfcConversionBasedUnit definitions |
What a Failing vs Passing IFC Export Looks Like
/* FAILING: IfcWall with no spatial containment, wrong geometry type for Reference View */
#100 = IFCWALL('3vFd8NzL7D...', #2, 'Wall-001', $, $, #101, #110, $, .STANDARD.); #101 = IFCLOCALPLACEMENT(#5, #102); #110 = IFCPRODUCTDEFINITIONSHAPE($, $, (#111)); #111 = IFCSHAPEREPRESENTATION(#12, 'Body', 'SweptSolid', (#112)); /* ERROR: 'SweptSolid' not permitted for IFC4 Reference View — must be 'Tessellation' */ /* ERROR: No IfcRelContainedInSpatialStructure links #100 to any IfcBuildingStorey */ /* ERROR: IfcWall has no IfcMaterialLayerSetUsage assigned */
/* PASSING: Correct Reference View export */
#100 = IFCWALL('3vFd8NzL7D...', #2, 'Wall-001', $, $, #101, #110, $, .STANDARD.); #101 = IFCLOCALPLACEMENT(#5, #102); #110 = IFCPRODUCTDEFINITIONSHAPE($, $, (#111)); #111 = IFCSHAPEREPRESENTATION(#12, 'Body', 'Tessellation', (#112)); /* OK: Tessellated geometry — IfcPolygonalFaceSet */ #112 = IFCPOLYGONALfaceset(#113, .T., (#114,#115,...), $); /* Spatial containment */ #200 = IFCRELCONTAINEDINSPATIALSTRUCTURE('7aB2kPqR...', #2, $, $, (#100), #50); /* #50 = IfcBuildingStorey */ /* Material */ #300 = IFCMATERIALLAYERSETUSAGE(#301, .AXIS2., .POSITIVE., 0., $); /* All WHERE rules pass. Schema conformance pass. MVD conformance pass. */
6 — bSDD, BCF, and the Broader buildingSMART Standards Ecosystem
IFC certification is the most well-known entry point into the buildingSMART ecosystem, but it is not the only one. A modern BIM software product that wants to compete in the full market needs to understand three additional standards that are increasingly referenced in government procurement and enterprise specifications.
| Standard | Full Name | What It Does | Certification Available | Market Relevance |
| bSDD | buildingSMART Data Dictionary | Cloud-hosted dictionary of building product properties and classifications. Links IFC property sets to specific product standards (ISO, EN, national). BIM objects in IFC files can reference bSDD definitions for standardised attribute meanings | No formal certification; API integration validation available | High and growing: EU Construction Products Regulation digital passports will use bSDD as backbone; Netherlands, Finland, UK piloting |
| BCF | BIM Collaboration Format | Open XML format for communication of model-based issues (clashes, RFIs, comments). A BCF file contains: camera viewpoint, markup text, screenshot, and IFC object reference. Allows issue tracking across different BIM software without re-exporting the model | BCF certification programme available (separate from IFC certification) | Critical for collaboration tools, CDE platforms, issue trackers, model checkers. ISO 19650 workflows assume BCF-based issue management |
| IDM | Information Delivery Manual (ISO 29481) | Framework for specifying what information needs to be delivered, when, by whom, and in what format during a BIM project. Used to define EIR (Employer’s Information Requirements) content in ISO 19650 workflows | No product certification; process framework | Important for CDE platforms and project management tools that want to support ISO 19650 workflows natively |
| IDS | Information Delivery Specification (buildingSMART standard) | Machine-readable specification format that defines exactly what IFC data a BIM model must contain for a specific project (e.g. “all walls must have FireRating property”). Enables automated model checking against project-specific requirements | IDS validation: bSI runs an open-source validator; software support is checked for compatibility | Rapidly growing: replaces manual EIR/BEP compliance checking; UK, Netherlands, Norway requiring IDS compatibility in procurement |
7 — Market Access: Which Governments Require buildingSMART Certification
This is the commercial core of the question: where in the world does buildingSMART membership and IFC certification translate directly into the ability to win government contracts? The answer varies significantly by country — and is changing fast as mandates become more specific.
| Country | IFC Certification Required? | bSI Membership Required? | Key Mandate / Reference | Market Priority |
| 🇬🇧 UK | Expected (ISO 19650 + UK BIM Framework specify IFC-certified tools) | Not mandatory but strongly aligned | UK BIM Framework; Construction Playbook; Building Safety Act (Golden Thread) | Very High |
| 🇸🇬 Singapore | Yes — CORENET X requires IFC-certified software for BCA e-submission | Not formally required but de facto | BCA CORENET X (IFC4.3-based e-submission system) | Very High |
| 🇰🇷 South Korea | Referenced in MOLIT BIM guidelines; IFC certification increasingly required in tenders | buildingSMART Korea chapter membership grows in importance | MOLIT BIM Guideline v2.0; K-BIM 2030 | Very High & Growing |
| 🇳🇱 Netherlands | Yes — Rijkswaterstaat (public works) and Rijksgebouwendienst require IFC-certified tools | buildingSMART Netherlands chapter active | NLCS, BIM Loket, RGD/RWS procurement requirements | Very High |
| 🇨🇫 Switzerland | SIA (Swiss Engineers & Architects Society) references IFC-certified tools; federal procurement requires openBIM | buildingSMART Switzerland active | SIA 2051 openBIM standard; federal infrastructure projects | High |
| 🇦🇺 Australia | NATSPEC BIM and federal government projects reference IFC certification | buildingSMART Australasia active | NATSPEC National BIM Guide; Australian Government BIM initiative | High |
| 🇩🇪 Germany | BIM Germany (BMVI stufenplan) references IFC; large public infrastructure projects (Deutsche Bahn, Autobahn GmbH) require IFC-compliant tools | buildingSMART Germany (bSI DE) active | BMVI BIM Stufenplan; Deutsche Bahn BIM-Anforderungen | High & Growing |
| 🇺🇸 USA | GSA requires IFC-compliant deliverables (not formal bSI certification); USACE references COBie and IFC but not bSI certification specifically | buildingSMART US active but not procurement-linked | GSA BIM Guide; NBIMS-US v3 (voluntary) | Medium (IFC compliance required; bSI cert not formally mandated) |
| 🇪🇺 EU Procurement | EU Directive 2014/24 allows procurement to require BIM; growing number of member states specify IFC-certified tools in OJEU tender notices | Varies by member state | EU BIM Task Group; national transpositions; EU Construction Products Regulation reform | High & Growing |
8 — The Developer’s Technical Roadmap: Building IFC Support from Scratch
If your team is building IFC support into a new product, the most important technical decision you will make is whether to build your own IFC parser/writer or use an open-source library. This decision has major implications for your certification timeline and long-term maintenance cost.
| Approach | Build Your Own Parser | Use Open-Source Library |
| Time to first IFC file | 6–18 months | Days to weeks |
| Certification risk | Very high — every WHERE rule, every geometry type must be implemented from scratch | Lower — libraries have been tested in production; known issues documented |
| Control | Full — you own every byte of the implementation | Partial — library limitations become your limitations |
| IFC version updates | Full re-implementation required for major schema changes | Library maintainers handle schema updates; you track library versions |
| Recommended for | Large established vendors with dedicated IFC engineering teams (Autodesk, Trimble, Nemetschek) | Startups and mid-size companies — strongly recommended |
Key Open-Source IFC Libraries
| Library | Language | Strengths | IFC Version Support | License |
| IfcOpenShell | C++ core; Python bindings | Most widely used; full geometry kernel; geometry conversion to OCC; comprehensive attribute access; Blender add-on included | IFC2x3, IFC4 ADD2, IFC4.3 | LGPL — commercial use OK |
| xBIM Toolkit | .NET (C#) | Strong .NET ecosystem integration; COBie export; model walking and querying; XBIM Xplorer viewer included | IFC2x3, IFC4 ADD2 | CDDL — commercial use OK |
| IFC.js / web-ifc | JavaScript / WebAssembly | Browser-native IFC parsing and rendering; Three.js integration; REST API backend support; ideal for web-based BIM viewers and SaaS platforms | IFC2x3, IFC4 ADD2 | Mozilla Public License — commercial use OK |
| ifcopenshell-python (bSDD module) | Python | Scripting, automation, batch processing; widely used in CI/CD pipelines for IFC validation pre-certification | All versions | LGPL |
| Open Design Alliance (ODA) | C++ / cross-platform SDK | Commercial-grade; includes DWG/DWF support alongside IFC; many certified products built on ODA. Paid membership required | IFC2x3, IFC4, IFC4.3 | Commercial (ODA membership ~$5,000–50,000/year) |
Practical Development Roadmap for a BIM Startup
| Month 0–2 | Integrate IfcOpenShell (or web-ifc for browser-based). Build basic read/write pipeline. Parse the bSI IFC schema EXPRESS file. Decide your target MVD. Read the MVD specification completely. |
| Month 2–4 | Run the bSI IFC Validator (validate.buildingsmart.org) on your first exports. Fix schema conformance and WHERE rule failures. Join buildingSMART as a member (Professional tier is fine at this stage) to access test documentation. |
| Month 4–7 | Systematically fix all geometry issues. Test your exports in Autodesk Revit, Solibri, Navisworks, ArchiCAD — real-world interoperability testing is often harder than passing the automated suite. Fix object classification (replace IfcBuildingElementProxy with correct typed entities). |
| Month 7–9 | Upgrade to Vendor Member tier. Submit certification application. Begin formal test runs. Engage bSI technical support for difficult edge cases. Expect 3–5 test cycles before passing. |
| Month 9–12 | Receive certification. Add to certified products register. Use the certification mark in marketing. Begin BCF and IDS support implementation. Register for national chapter events to build market relationships. |
9 — Common Failure Modes: Why BIM Startups Fail Certification
A significant proportion of first-time certification applications fail, or pass only after multiple cycles of fixes. The failure patterns are consistent enough to document. Understanding them before you start developing will save months of rework.
| Failure Mode | What Happens | Why It Happens | Prevention |
| IfcBuildingElementProxy overuse | 60–90% of model elements are exported as the catch-all IfcBuildingElementProxy type | The internal domain model does not distinguish element types that map to IFC types; lazy implementation exports everything as generic | Build an explicit IFC type mapping table early. Every element category in your domain model needs a corresponding IfcProduct subtype |
| Wrong geometry type for MVD | Exports IfcExtrudedAreaSolid (parametric) for Reference View certification (which requires tessellated geometry) | Developer reads IFC schema without reading MVD specification; implements what IFC allows, not what the MVD restricts | Read the MVD specification document before implementing geometry export. The MVD, not the IFC schema, defines what is valid for certification |
| Missing spatial structure | Elements exist in the file but are not connected to IfcSite → IfcBuilding → IfcBuildingStorey hierarchy | The software’s internal data model does not enforce spatial hierarchy; elements are exported without placement context | Require spatial hierarchy creation before IFC export. Every product must have an IfcRelContainedInSpatialStructure or IfcRelAggregates relationship |
| GUID duplication | Multiple elements share the same GlobalId (IfcGUID) | Copy/paste element creation propagates the same GUID to new elements; no UUID generation on copy | Generate a fresh RFC 4122 UUID (compressed to IfcGUID format using the base64 algorithm in the IFC spec) for every new element. Never copy GUIDs |
| Floating-point geometry issues | Geometry validation fails with messages like “degenerate face”, “open shell”, “non-manifold solid” | Accumulated floating-point errors in geometry calculations produce faces with near-zero area or edges that do not close properly at the required precision tolerance (usually 1e-5 metres) | Use IfcOpenShell’s geometry kernel for tessellation rather than rolling your own. Run geometry validation checks before export using IfcOpenShell Python API |
| Unit declaration omission | IfcUnitAssignment is incomplete; importing software cannot determine whether lengths are in millimetres or metres | Developer assumes units are obvious from context; IFC requires explicit declaration of every unit used in the file | Always include IfcUnitAssignment with complete SI unit declarations in the IfcProject entity. Test with a viewer that strictly enforces units (Solibri is strict) |
10 — Business Case: The ROI of buildingSMART Membership and IFC Certification
The costs are real. The ROI depends entirely on which markets you are targeting. Here is a framework for evaluating whether the investment makes sense for your specific situation.
Total Cost of Entry (Typical BIM Startup, Year 1)
| Cost Item | Estimated Amount | Notes |
| bSI International membership (Vendor tier) | €5,000–15,000/year | Depends on organisation size and tier selection |
| National chapter membership (e.g. bSI Korea, bSI UK) | €500–5,000/year | Per chapter; join 1–2 priority markets first |
| IFC certification fee (per MVD, per version) | €1,500–3,500 | Lower for higher membership tiers |
| IFC development engineering cost (internal) | $50,000–200,000 (one-time) | Highly variable; using IfcOpenShell significantly reduces this |
| Ongoing IFC maintenance (annual) | $20,000–80,000/year | Schema updates, bug fixes, re-certification on major releases |
| Total Year 1 (excl. internal dev) | €7,000–24,000 | Membership + certification fees only |
Market Access Value by Target Market
| Target Market | Without bSI Certification | With bSI Certification | Verdict |
| Government procurement (UK, NL, SG, KR) | Excluded from tender qualification in many cases | Qualifies for IFC-compliant software lists; eligible for government tender evaluation | Non-negotiable |
| Large enterprise (Tier 1 contractors, global AEC firms) | IFC interoperability questioned; IT procurement requires evidence of certification | Passes IT procurement checklist; trusted by BIM managers; easier piloting and onboarding | Essential |
| Mid-market AEC firms (50–500 employees) | Some buyers will accept vendor claims; many ask “are you certified?” | Removes an objection in sales process; shortens procurement cycle | Highly recommended |
| US private sector only | Viable; US private sector does not mandate certification | Differentiator, not a barrier; improves credibility | Optional but beneficial |
| Small practices / freelance AEC professionals | Target audience rarely requires certification evidence | Nice to have; won’t move purchase decisions at this tier | Defer |
What Every BIM Startup Needs to Know
| › | buildingSMART membership is the commercial door; IFC certification is the technical key. You need both to access government and enterprise BIM markets in the UK, EU, Korea, Singapore, and Australia |
| › | IFC is a relational graph, not a file format — implementing it correctly requires reading the schema, the MVD specification, and the WHERE rules before writing a single line of export code |
| › | Use IfcOpenShell or xBIM as your geometry and parsing foundation — building your own IFC parser from scratch is a 12–18 month detour that most startups cannot afford |
| › | The certification process is self-service and iterative — run the bSI validator early and often, not just before you submit. Most certification failures are preventable with earlier testing |
| › | IFC certification is the entry ticket, not the finish line. BCF, IDS, and bSDD support are becoming the next tier of requirements in advanced markets — plan for them in your roadmap |
| › | The buildingSMART chapter network is an underutilised strategic asset — the relationships with government BIM programme managers, large system integrators, and enterprise BIM managers that you build there are worth more in the medium term than the certification mark itself |
About This Article
This article is part of The AEC Intelligence Report, examining technology, standards, and market strategy in architecture, engineering, and construction. Published on the AI Workflow Blog.
By The AEC Intelligence Editorial Team · AI Workflow Blog · May 2026
Sources / References
› buildingSMART International — Membership information, IFC certification programme, Technical Rooms — buildingsmart.org/membership
› buildingSMART International — IFC Validator (validate.buildingsmart.org) — validate.buildingsmart.org
› buildingSMART International — Certified Products Register — buildingsmart.org/compliance
› ISO 16739-1:2018 — Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries — iso.org
› ISO 16739-1:2024 — IFC4.3 (including IFC Rail) — iso.org
› buildingSMART International — IFC4 ADD2 TC1 Model View Definitions (Reference View, Design Transfer View) — buildingsmart.org
› buildingSMART International — bSDD (buildingSMART Data Dictionary) API documentation — buildingsmart.org/bsdd
› buildingSMART International — BCF (BIM Collaboration Format) specification and certification — buildingsmart.org/bcf
› buildingSMART International — IDS (Information Delivery Specification) standard and validator — buildingsmart.org/ids
› IfcOpenShell — Open-source IFC library documentation — ifcopenshell.org
› xBIM Toolkit — .NET IFC toolkit documentation — docs.xbim.net
› IFC.js / web-ifc — JavaScript IFC library — ifcjs.github.io
› Open Design Alliance — Commercial CAD/BIM SDK including IFC support — opendesign.com
› BIMForum / AIA — Level of Development (LOD) Specification 2023 — bimforum.org
› Singapore BCA — CORENET X IFC4.3 e-submission requirements — bca.gov.sg
› Netherlands BIM Loket — OpenBIM requirements and IFC certification guidance — bimloket.nl
› buildingSMART Korea — K-BIM 2030 IFC requirements alignment — buildingsmart.or.kr
› ISO 10303-11:2004 — EXPRESS language reference manual (IFC schema definition language) — iso.org
.png)
Comments
Post a Comment