ISO 16739-1:2024 (IFC4.3): Architects' Guide to the IFC Schema Standard

ISO 16739-1:2024 is the ISO standard that publishes the IFC4.3 schema, the machine-readable format for building model exchange. IFC4.3 adds infrastructure domains (rail, road, port) to the schema for the first time. Most Revit and ArchiCAD installations still export IFC4 Add2 TC1 (the 2018 edition): tool adoption lags ISO 16739-1 by one to three years.

Key numbers at a glance

ISO 16739-1 is a versioned standard: each edition corresponds to a specific IFC schema release. The table above maps ISO editions to IFC schema releases and adoption status. The 2024 edition introduced IFC4.3, a major expansion adding new entity classes for rail, road, bridge, port, and water infrastructure. Prior editions covered only buildings and site elements. The standard costs approximately CHF 222 per copy through ISO, BSI, DIN, or AFNOR. The full IFC4.3 schema is freely browsable at buildingSMART’s technical site (standards.buildingsmart.org) without purchasing the ISO publication. The ISO standard provides institutional weight for contractual and regulatory citations. For day-to-day technical work, looking up property sets or checking entity relationships, the buildingSMART HTML reference is the practical tool. Both sources contain the same technical content: the ISO publication charges for the institutional wrapper and citation authority.

What is ISO 16739-1 and what does it standardize?

ISO 16739-1 is the International Organization for Standardization publication of the Industry Foundation Classes schema, required to define data structures for construction and facility management information exchange. buildingSMART International maintains the schema; ISO provides the institutional publishing framework. The standard specifies four elements: the EXPRESS data schema (formal entity and attribute definitions), conformance classes (what any compliant software implementation must support), serialization formats (how IFC data is written to files), and a normative reference framework for jurisdictional adoption. ISO 16739-1 does not specify what data must be present for any specific exchange: that function belongs to IDS (Information Delivery Specification). ISO 16739-1 does not govern information management workflows: that is ISO 19650. ISO 16739-1 defines the container. IDS defines what the container must hold. ISO 19650 governs the supply chain that moves containers between parties. The three standards are complementary and typically required together in public-sector BIM mandates.

Which jurisdictions mandate ISO 16739-1 compliance?

DataDrivenAEC’s analysis of major public-sector BIM mandates shows seven jurisdictions or regions have made ISO 16739-1 the required or referenced IFC schema standard. The UK Government BIM Mandate requires ISO 16739-aligned IFC submissions on centrally-procured public projects. Singapore’s CORENET X electronic submission system has required IFC since 2015, mandating ISO 16739-1 for all public-sector building submissions. The Federal Republic of Germany’s BIM Strategy names DIN EN ISO 16739-1 as the binding schema reference. The European Union’s EPBD recast and the Level(s) sustainability framework reference ISO 16739 for digital model submissions supporting whole-life carbon calculations. Australasia and New Zealand public-sector BIM frameworks reference ISO 16739-1 through buildingSMART national certification modules. Common to all mandates: the requirement specifies the schema standard (ISO 16739-1) but leaves authoring tool selection open. Contracts must additionally name the target IFC schema release (IFC4 Add2 TC1 or IFC4.3) to be unambiguous.

IFC schema versions: what is current and what do tools actually export?

ISO 16739-1:2024 corresponds to IFC4.3, the current schema. ISO 16739-1:2018 corresponds to IFC4 Add2 TC1, the version most authoring tools produce by default. Tool adoption lags the ISO standard by one to three years. Revit and ArchiCAD users configuring an IFC export today typically produce IFC4 Add2 TC1 (ISO 16739-1:2018), not IFC4.3 (ISO 16739-1:2024). The IFC4 base (ISO 16739:2013) is legacy status. Projects with contracts specifying “IFC4” without a sub-version should clarify whether IFC4 base, IFC4 Add2 TC1, or IFC4.3 is required: the three releases differ in entity count, property set definitions, and serialization rules. Infrastructure projects (rail, road, bridge) are the first domain where IFC4.3 is operationally required rather than optional. Building-only projects can exchange successfully in IFC4 Add2 TC1. Verify recipient software’s stated support before specifying IFC4.3 on a contract to avoid exchange failures at submission.

What are common mistakes when specifying IFC model exchange?

1. Specifying ‘IFC4’ without a sub-version. IFC4 covers three distinct schema releases (base 2013, Add2 TC1 2018, IFC4.3 2024). A contract that specifies “IFC4” without a sub-version is ambiguous and interpreted differently by different parties. Name the ISO edition explicitly: ISO 16739-1:2018 for IFC4 Add2 TC1, ISO 16739-1:2024 for IFC4.3.

2. Treating schema compliance as content completeness. A schema-valid IFC file does not mean the model contains required data for any exchange. Content completeness is specified by IDS (Information Delivery Specification), not ISO 16739-1.

3. Conflating ISO 16739-1 with ISO 19650. ISO 16739-1 specifies the data schema. ISO 19650 governs the information management process. Both operate simultaneously on the same project at different layers.

4. Specifying IFC4.3 before verifying tool support. Tool adoption lags ISO publication by one to three years. Specifying IFC4.3 without confirming sender and recipient software support risks exchange failure at model submission.

5. Buying the ISO document for technical reference. The full IFC4.3 schema is freely browsable at standards.buildingsmart.org. Purchase ISO 16739-1 only when a contract or regulation requires a specific ISO citation number.

How DataDrivenAEC automates code compliance checking

This compliance check takes 2–4 hours manually. DataDrivenAEC builds custom agents that run this check on your drawing set and deliver the findings as a structured report. See all agents →

Frequently asked questions

What is the difference between ISO 16739-1:2018 and ISO 16739-1:2024?

ISO 16739-1:2018 corresponds to the IFC4 Add2 TC1 schema, the current production standard for building projects. ISO 16739-1:2024 corresponds to IFC4.3, which adds hundreds of new entity classes for rail, road, bridge, port, and water infrastructure. For building-only projects, IFC4 Add2 TC1 remains the practical choice because most Revit and ArchiCAD installations produce it by default. Specify the sub-version explicitly in contracts: “IFC4” without qualification spans three distinct schema releases and is ambiguous.

Is the IFC4.3 schema available without purchasing ISO 16739-1:2024?

Yes. buildingSMART International publishes the full IFC4.3 schema freely at standards.buildingsmart.org, including entity definitions, property sets, and relationship documentation. The ISO publication (ISO 16739-1:2024, approximately CHF 222) provides no additional technical content. Purchase the ISO document only when a contract or regulatory submission requires a specific ISO 16739-1 citation number rather than a buildingSMART reference.

Which jurisdictions mandate IFC submissions aligned with ISO 16739-1?

Singapore’s CORENET X system has required ISO 16739-aligned IFC submissions for public-sector projects since 2015. The UK Government BIM Mandate requires ISO 16739-aligned IFC on centrally-procured public projects. Germany’s national BIM Strategy names DIN EN ISO 16739-1 as the binding reference schema. The EU EPBD recast references ISO 16739 for digital model submissions. Australasia and New Zealand public-sector frameworks reference ISO 16739-1 through buildingSMART national certification modules.

What does ISO 16739-1 not cover?

ISO 16739-1 does not specify what data must be present for any specific use case: that is IDS. ISO 16739-1 does not govern information management workflows or project procedures: that is ISO 19650. ISO 16739-1 does not specify sustainability calculation methods: that is EN 15978 (whole-building LCA) and EN 15804 (product EPDs). A schema-valid IFC file can be completely empty of meaningful data: schema compliance and content completeness are independent requirements.

What is the three-IDS pattern for sustainability data in IFC models?

buildingSMART’s use-case model (UCM 3343) recommends splitting sustainability information across three IDS files rather than embedding everything in one model: a Facility IDS for building systems and spaces, a Product IDS for material types, and a Declaration IDS for EPDs per ISO 21930. The three-IDS pattern prevents single-model file sizes from becoming unmanageable and allows EPD data to be versioned independently from the geometric model. See the buildingSMART IDS 1.0 standard (published June 2024) for the normative specification.